The playbook
Mobile SEO: Template and Field Guide
This mobile SEO template turns a broad task into a record another person can use. It captures page, mobile task, issue, 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
Check the complete content and action path on a narrow screen. A desktop menu hidden by CSS needs an accessible alternative. Phone links, forms, expanded sections, and sticky controls should remain usable without horizontal overflow or overlays covering the action.
Copyable worksheet
| Field | Entry instructions |
|---|---|
| page | Record the page associated with this page or query record. Use a stable reference so later updates can be matched. |
| mobile task | Record the mobile task associated with this page or query record. Keep the value specific enough for another owner to interpret. |
| issue | Record the issue associated with this page or query record. Keep the value specific enough for another owner to interpret. |
| repair | Record the repair 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 page. Use the same reference throughout the record so notes are not attached to the wrong item. Then compare mobile content navigation and metadata. This establishes the information required before the worksheet becomes a request for action.
Next, test forms and key tasks on narrow screens. Use the observed problem and evidence fields to explain why that step is needed. A useful entry describes an actual condition, such as removing important content from the mobile experience, rather than a broad instruction to “improve performance.”
Finally, fix obstructive overlays and inaccessible controls. Put preserve useful content and adapt presentation to the viewport 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 | Removing important content from the mobile experience |
| Action | Preserve useful content and adapt presentation to the viewport |
| First check | Compare mobile content navigation and metadata |
| Follow-up check | Fix obstructive overlays and inaccessible controls |
| Outcome to define | mobile task completion |
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 mobile task 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 mobile task completion connected to the item so the team can later assess whether the action was useful.
Search results and indexing decisions are not controlled by the publisher. Record what your team changed and what was observed afterward. Avoid turning a correlation between a release and a traffic change into a claim of proven causation.
Skip the manual steps. Let AgentixSEO run this for every client.
Start now