A Browser Tab Workflow for a Technical SEO Audit

Define the audit scope and critical pages

List the production host, important templates, priority pages and recent changes. Decide whether the audit covers a launch, migration, traffic decline or routine health check. Keep staging and production tabs in separate groups so evidence is not attributed to the wrong environment.

Record the date, device and account context for tools that personalize results. An audit finding without its environment can be difficult to reproduce.

Check discovery and indexation first

Verify robots.txt, page-level robots directives, HTTP status, canonical URL, sitemap presence and internal links for priority pages. These checks come before cosmetic metadata because a page that cannot be crawled or is canonicalized elsewhere may not compete as intended.

Save one representative passing URL and every distinct failing pattern. Avoid collecting hundreds of identical tabs when one template-level issue explains them.

• Google Search technical requirements

Inspect rendering and structured data

Confirm that the main content, title, links and structured data are present in rendered HTML. Validate schema against the visible page, including dates, author, image and canonical URL. Structured data should describe content a reader can actually find.

Capture the exact validation result and affected template. A warning may be optional while an invalid required property can block a rich-result feature, so record impact rather than treating every message equally.

Review performance in context

Test representative templates and note whether a slow resource is shared across the site or unique to one page. Separate lab measurements from field data. A single run can reveal a debugging clue but does not establish the experience of every visitor.

Keep performance work connected to the page's purpose. Compressing a useful image or removing unused code can help; hiding meaningful content to improve a score can harm the reader.

Idea: one evidence card per issue

For each issue, record affected scope, example URL, observed result, expected result, business impact, owner and verification step. Link screenshots or exports only when they add information beyond the written finding.

Group duplicates under the same root cause. A concise list of reproducible issues is easier for developers to fix and for reviewers to retest than an unfiltered crawler export.

• Prepare an SEO content brief from sources

Retest and preserve the decision trail

After a fix, repeat the original check on the example URL and another page using the same template. Record the deployment or date and note any remaining limitation. Close the investigation tabs only after the evidence and result are attached to the issue.

Finish with a short summary of critical, high and later work. Technical SEO is an ongoing system, so the audit should make the next review faster instead of starting from zero.

• Google SEO starter guide