> ## Documentation Index
> Fetch the complete documentation index at: https://docs.synscribe.com/llms.txt
> Use this file to discover all available pages before exploring further.

# How to run a technical SEO audit

> Audit a published page against the checklist before you count it as done.

Run a technical SEO audit after a page is published to confirm it's actually readable and rankable — ask Pi with the `account-quality-control` skill (`do a technical SEO audit on [page URL]`) or work the checklist by hand. It checks the few things that change how a human and an LLM read the page in search results: meta title, meta description, and H1 (primary keyword first), plus canonical, schema, sitemap inclusion, and internal discoverability. Fix the non-optional findings, then re-audit to verify. Ignore the hundreds of cosmetic "issues" generic tools throw — the checklist below is the bar.

> **Good to know:** Most technical-SEO tools throw hundreds of "issues" that don't change anything.
> The few that matter are the ones that affect how a human and an LLM read the page in search results.
> See [Part 1 §1.11 — Definition of Done](/theory/definition-of-done).

## Ask Pi to run it

```text theme={null}
do a technical SEO audit on [page URL]
```

Pi checks the page against the list below, reports findings, and can fix most of them. Fix the
non-optional findings, then re-audit to verify the fixes.

## The checklist

**The three that matter most** (a human and an LLM look at these first in the results and decide
"is this relevant to me?"):

* [ ] **Meta title** matches the title, primary keyword first
* [ ] **Meta description** matches the description, contains the keyword (or a variant)
* [ ] **H1** matches the title, primary keyword first

**The rest:**

* [ ] Canonical link is correct
* [ ] Primary keyword (or variant) in the first paragraph
* [ ] Featured image is the OG image (preferred); OG image title is set
* [ ] Table of contents present (preferred)
* [ ] Headings make sense and flow logically (Ahrefs toolbar, then Content)
* [ ] `BlogPosting` / `Article` JSON-LD present (blog posts)
* [ ] **FAQ JSON-LD present** — required on landing pages *(future item for blog posts — no FAQ
  export yet)*
* [ ] Page is in `sitemap.xml`
* [ ] Page is **discoverable by clicking from the homepage** (via a hub page) — and, for pages
  with collapsed link lists, links are still present in the DOM. See
  [Part 1 §1.8 — internal linking](/theory/internal-linking-authority).

**Landing-page hub pages additionally:** all elements are DOM-readable (may be visually hidden).

## Don't chase junk

If a tool hands you hundreds of fixes that don't change the experience for a human or an LLM, ignore
them. The list above is the bar. Log genuinely-deferred work as a Linear ticket rather than
gold-plating.

## Make it a gate

> Treat the audit as a Definition-of-Done gate, not optional polish. Run it on every
> published page, fix all non-optional findings, and re-audit to confirm before moving on.

**Related:** [2.5.1 Publish & set the live URL](/platform/publish-set-live-url) · [2.5.3 Index on GSC + sitemap](/platform/index-gsc-sitemap)