The playbook
Technical SEO: Checklist
Use this technical SEO checklist before a new release, a handoff, or a scheduled review. Its purpose is to verify the decisions that affect eligible important pages. Check an actual page or query record; a box marked complete without evidence does not show that the customer journey works.
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.
Before you use the checklist
Name the exact item being checked and its purpose. Gather template, status, indexability, rendered content. If one of those details is unknown, mark it as unknown and assign a way to resolve it. An invented value makes the checklist look complete while weakening every later decision.
Working checklist
| Check | Evidence to keep | Responsible role |
|---|---|---|
| Inspect server responses for important page types | A dated observation showing how template was verified | SEO lead |
| Compare rendered content with visible browser content | A dated observation showing how status was verified | content or development owner |
| Validate canonical indexability and discovery signals | A dated observation showing how indexability was verified | analytics owner |
Check the failure path
- Look specifically for this failure: checking only the homepage while templates fail elsewhere.
- Sample each template and trace failures to the shared component. Record the actual correction, not just the intention to make it.
- Repeat the affected task after the correction and check rendered content.
- Make sure the next owner can find the decision and supporting evidence.
Use three outcomes for each check
Mark an item as complete only when the expected behavior or information has been observed. Mark it as incomplete when a required condition is absent. Use not applicable when the condition genuinely does not belong to the chosen scope, and write a short reason. These states keep a review useful without forcing every process into an identical mold.
For example, if the check is “Inspect server responses for important page types,” a meeting about the subject is not the evidence itself. Retain the relevant template and status, the decision made from them, and the result of checking that decision. The record should allow someone who missed the meeting to understand what changed.
Decide what must be resolved first
An incomplete item that prevents make public website content accessible and interpretable to search crawlers deserves attention before a cosmetic improvement. Assign an owner and a next action to that issue. Keep optional refinements visible, but do not let them obscure a failure in the core process.
Close the review
Recheck corrected items and note anything still uncertain. The checklist is finished when the next owner understands what was verified and what remains open. Follow eligible important pages using a consistent definition so later reviews can connect execution quality with useful results.
Keep a dated record of the page or query being examined. Search interfaces and external references can change. A saved observation should include enough context to distinguish an old issue from the current state.
Skip the manual steps. Let AgentixSEO run this for every client.
Start now