SEO tools: a template for recording decisions and sources

What to take away

Use this SEO tools template as a decision recordeach row should have an owner, source and review date; keep tool choices distinct from evidence.
Use the six core columnsdecision, source, date, owner, method and review.
Name the source type and the specific page, so the template outlives the subscription.
Where no published figure exists, label the example and its number as illustrative.

The columns every row carries

Every row needs six columns, and the first one is the decision the row supports. A template that opens with a tool list usually ends as a shopping list, so put the decision in the row heading before you name any source.

Column	What goes in it	Why it earns its place
Decision	Which keyword set to track, which competitors to watch, which content gaps to fund	Keeps the row in a budget conversation, not a feature comparison
Source	The source type and the specific page	Names survive; product names date quickly
Date	The export or quote date	An undated number gets re-litigated in the next meeting
Owner	The person who answers when the figure is questioned	The owner is not necessarily the person who typed it in
Method	An export, a manual check or a screenshot	Tells the next reader how much weight the number can carry
Review	The cadence, written into the template header	Lets the rule travel with the file

Copyable blank template

Copy the header and empty row into your spreadsheet or document:

Decision	Source	Date	Owner	Method	Review

Worked tracking example

This illustrative row shows how the fields work together; replace the entries with your own details:

Decision	Source	Date	Owner	Method	Review
Track the selected keyword set	Google Search Console Performance report	Date of export	Named SEO owner	Export the Performance report	Next scheduled review

Every row needs three columns

Sourcethe specific page, not the tool
Datewhen the figure was captured
Ownerwho answers when questioned
Methodexport, manual check or screenshot
Cadencequarterly for costs and competitors
Cadencetwice a year for content plans

A source without a date is an opinion. The owner is the person who answers when the figure is questioned, so name them before the template is shared, not after the first challenge.

Examples of source choices

The tracking, competitor, budget and content examples show how to record source names, dates and review rules.

Source by template column

Column

Tracking: Own analytics
Budget: Invoice or price page
Competitors: Vendor feature docs
Content: GOV.UK guidance
Rationale: Moz education

Source

Tracking: Export date
Budget: Quote date
Competitors: Access date
Content: Retrieval date
Rationale: Publication date

Date rule

Tracking
Budget
Competitors
Content
Rationale

For the tracking row, the decision is which keyword set to follow. Your own analytics, the Google Search Console Performance report (Search Console data) and CRM records are the cheapest sources to defend, because you control the definitions. Record the export date beside each one.

For the competitor row, vendor documentation does the work. Semrush's competitor analysis features document definitions you can copy straight into a template, so a competitor set means the same thing to everyone reading it.

For the budget row, licence and seat costs belong beside the source that quotes them: a supplier price page, an invoice or a signed order. The £400 a month figure for a seat-based rank tracker is illustrative, not a supplier quote; do not record it as an actual price. For a real cost, record the source and the date it was quoted. For renewal context, see the licence audit.

Content rows lean on official guidance. GOV.UK's content design guidance puts readers first and gives a plain-language test for whether a page earns its place in a content plan. Record the linked page itself in the Source field, not a broad resource-family label.

Settling clashes between sources

Rows sometimes pull in different directions. The table settles the clashes that come up most often when filling in a source column.

Choose

The competitor set must survive a licence change: A named list in your own sheet, refreshed from a vendor feature
Finance wants a defensible content budget: First-party analytics plus published guidance
Rankings span several markets: One source per market, recorded with its date
A vendor claim cannot be verified: A labelled illustrative example
Renewal falls in the next quarter: A licence and seat column inside the template

Avoid

The competitor set must survive a licence change: A list held only inside the tool
Finance wants a defensible content budget: Undated vendor blog posts
Rankings span several markets: Averaging positions from different providers
A vendor claim cannot be verified: Presenting the claim as measured data
Renewal falls in the next quarter: Renewing before the review date is set

Choosing a source for a row

Must the figure survive a licence change?

Yes

Name the list in your own sheet

Keep the vendor list with its date

Review rhythm and the blank-cell problem

Set a review cadence you can keep: quarterly for licence costs and competitor sets, twice a year for content plans. Write it into the template header so it travels with the file.

The common failure is a source column left blank because the tool obviously supplies it. Months later nobody can tell whether a figure came from a vendor dashboard or a manual check.

The second failure is naming tools in the source column. Tools change names, merge and get replaced. Name the source type and the specific page instead.

When two rows disagree, compare the source type, method and date recorded in the template. The strategy framework provides related context.

Common questions

How many sources should a planning template hold?

Enough to cover each decision once. Four families cover most plans: first-party data, vendor documentation, official guidance and third-party education.

Should the template name specific SEO tools?

This template records the evidence behind decisions, so name the source page in the Source column rather than treating it as a tool list. If your wider plan also tracks licences, record a tool name in a separate licence field.

How often should sources be reviewed?

Match the review to the cost of being wrong. Licence and price rows warrant a quarterly check; content rationale rows can wait six months. Record the date either way.

What if a source stops publishing?

Replace a source before the next review, not after. Record the replacement page, the date you checked it and the reason for the change.