The playbook
JavaScript SEO: Template and Field Guide
This JavaScript SEO template turns a broad task into a record another person can use. It captures route, rendered content, metadata, 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
Load a deep URL directly rather than navigating from the homepage. Check whether the correct title, content, links, and status appear. Client-side navigation can mask a server-routing problem that a direct visitor or crawler encounters immediately.
Copyable worksheet
| Field | Entry instructions |
|---|---|
| route | Record the route associated with this page or query record. Use a stable reference so later updates can be matched. |
| rendered content | Record the rendered content associated with this page or query record. Keep the value specific enough for another owner to interpret. |
| metadata | Record the metadata associated with this page or query record. Keep the value specific enough for another owner to interpret. |
| response | Record the response 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 route. Use the same reference throughout the record so notes are not attached to the wrong item. Then compare source rendered output and browser content. This establishes the information required before the worksheet becomes a request for action.
Next, test links metadata and route responses on deep pages. Use the observed problem and evidence fields to explain why that step is needed. A useful entry describes an actual condition, such as returning the same empty shell or metadata for every route, rather than a broad instruction to “improve performance.”
Finally, inspect errors that prevent meaningful content from loading. Put render page-specific content and validate direct URL access 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 | Returning the same empty shell or metadata for every route |
| Action | Render page-specific content and validate direct URL access |
| First check | Compare source rendered output and browser content |
| Follow-up check | Inspect errors that prevent meaningful content from loading |
| Outcome to define | routes with complete rendered content |
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 rendered content 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 routes with complete rendered content 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