The playbook
Technical SEO: Template and Field Guide
This technical SEO template turns a broad task into a record another person can use. It captures template, status, indexability, then connects that information to a decision. Copy the table into your working document or system and create a separate record for each item in scope.
Put the task in context
A useful diagnostic compares the HTTP response, the rendered page, and the intended canonical URL. A page can return success while displaying an application error. Likewise, a visible page can carry an unintended noindex directive. Record these as separate observations rather than one pass/fail score.
Copyable worksheet
| Field | Entry instructions |
|---|---|
| template | Record the template associated with this page or query record. Use a stable reference so later updates can be matched. |
| status | Record the status associated with this page or query record. Keep the value specific enough for another owner to interpret. |
| indexability | Record the indexability associated with this page or query record. Keep the value specific enough for another owner to interpret. |
| rendered content | Record the rendered content associated with this page or query record. Keep the value specific enough for another owner to interpret. |
| Decision field | Entry instructions |
|---|---|
| Observed problem | Describe the actual condition and where it was observed. |
| Recommended action | State the smallest action that resolves the documented problem. |
| Evidence | Link to the record, observation, or test supporting the action. |
| Owner and next review | Name the accountable person and when the decision should be revisited. |
How to complete the worksheet
Begin with template. Use the same reference throughout the record so notes are not attached to the wrong item. Then inspect server responses for important page types. This establishes the information required before the worksheet becomes a request for action.
Next, compare rendered content with visible browser content. Use the observed problem and evidence fields to explain why that step is needed. A useful entry describes an actual condition, such as checking only the homepage while templates fail elsewhere, rather than a broad instruction to “improve performance.”
Finally, validate canonical indexability and discovery signals. Put sample each template and trace failures to the shared component in the action field only when it addresses the observed condition. If the problem is different, change the action. The template is a structure for judgment, not a reason to apply the same fix everywhere.
Illustrative completed decision
| Part | Illustrative entry |
|---|---|
| Problem | Checking only the homepage while templates fail elsewhere |
| Action | Sample each template and trace failures to the shared component |
| First check | Inspect server responses for important page types |
| Follow-up check | Validate canonical indexability and discovery signals |
| Outcome to define | eligible important pages |
Adapt the fields without losing meaning
You can add fields required by your team, but each should change a decision or preserve necessary context. Keep factual observations separate from recommendations. If status changes, record the new value and its effective date instead of silently rewriting the context of an earlier decision.
Use the record in a handoff
Ask the receiving owner to explain the next action using only the worksheet. Missing context becomes visible quickly during that exercise. Repair the record before applying the structure to a larger batch. Keep eligible important pages connected to the item so the team can later assess whether the action was useful.
Keep page purpose visible throughout the work. A technically valid page can still fail to answer the reader’s question. Separate access and discovery problems from content problems so that the assigned action matches the cause.
Skip the manual steps. Let AgentixSEO run this for every client.
Start now