/seo-page-sections

name: seo-page-sections
description: "Generic page auditor and entry point for every page type: runs spec, audit, competitor benchmark and build. Phase 1 spec: site archetype (Shopify, Webflow or WordPress, marketplace), the page types it needs, then the page type's block list plus the common spec and the site-level, header and footer rules (SEC IDs). Phase 2 audit: section_audit.py and seo_audit.py mark rows Pass, Fail or Not verifiable. Phase 3: page_benchmark.py on 3-5 competitors of the same page type. Phase 4: write the missing blocks (FAQ, breadcrumb, definitions, comparison and spec tables, reviews, trust badges, CTA, cross-links), then re-run the scripts as the acceptance test. Covers 21 page types: routes product, collection, service, location, comparison, top 10, segment, article and homepage copy to their dedicated skills; owns pricing, about, contact, blog hub, call, author, free tool, wall of love, affiliate, 404, listing, login. Use when a clean page underperforms, to find the pages and blocks a site lacks, or for a checklist."
license: MIT
metadata:
  author: "Sorank (https://sorank.com)"
  version: "2.0.0"

What is missing on this page, and on this site

Most pages that fail do not fail on tags. They fail because a block that buyers and AI assistants both need is simply absent: no FAQ, no breadcrumb, no comparison, no price in text, no definitions. Most sites that fail are missing a whole page type nobody audited because it does not exist. This skill specifies what a page of a given type must contain, audits it, benchmarks it against the competitors that rank, and writes the missing blocks.

Two audits, two altitudes. `seo-geo-audit` asks "is this site healthy" (crawl, speed, indexation, tags, schema). This skill asks "does this site have the pages it needs, and does each page contain the blocks a page of its type must contain". Run it when the technical layer is already fine and the page still underperforms, or when the deliverable is a build list rather than a diagnosis. It is the entry point for every page type that has no dedicated skill, and for site-level audits.

Company knowledge first (Obsidian)

If the working environment contains an Obsidian vault or any local knowledge base (a folder of .md notes, often with a .obsidian directory), read the relevant notes before writing any block: real product facts, real prices, real client names, positioning, the competitors worth comparing against, and the SEO action log. Every block this skill generates asserts facts about the business, so unsourced invention is the main failure mode. Ground each block in the vault, and append what was added to the vault's SEO action log at the end of the session.

When to use

• Someone asks what is missing on their site, on a page, or what to add to improve it.
• A page is technically clean, indexed, and still does not rank or get cited.
• A page is being built from scratch and needs its mandatory block list.
• A client-facing checklist is needed: "here is what to add, block by block".
• A template is being designed (Figma, theme, page builder) and the block list must be decided before the design.

When the page type has a dedicated skill (Phase 1, Step 2 table), this skill identifies the type and the site-level gaps, then routes the full page work there. Other adjacent work:

| Need after the gap report | Skill | |---|---| | Full page rewrite of a type with a dedicated skill, not just missing blocks | the matching seo-content-* skill, seo-local | | Real questions to put in the FAQ | seo-keyword-research | | Schema for the new blocks | seo-schema-markup | | Cross-link targets and anchors, header and footer link plan | seo-internal-linking | | Blocks not visible in raw HTML, speed, crawl | seo-technical | | Whole-site health rather than one page | seo-geo-audit | | Whether the new blocks got the page cited | geo-visibility, geo-tracking |

Phase 1. The spec

Built in three steps, because the most expensive gap is not a missing block, it is a page type that does not exist at all. That gap is invisible when auditing only the pages that already exist.

**Step 1, the archetype.** Read `references/site-archetypes.md` now. It gives the three archetypes (Shopify store, Webflow or WordPress site, marketplace), the page inventory each one needs, block lists for the archetype-specific page types, the header and footer rules, and the persuasion levers that apply site-wide. List the page types the site should have and does not (SEC-01) before auditing anything else.

**Step 2, the page type.** Everything downstream depends on this. A missing comparison table is a serious gap on a comparison page and irrelevant on a contact page.

| Type | Recognize it by | Block list (the spec) | Full spec, audit and build | `--type` | |---|---|---|---|---| | product | One sellable item, buy box, SKU, Product schema | matrix 1 | seo-content-product-page | product | | collection | A list of products or listings, filters, category URL | matrix 2 | seo-content-collection-page | collection | | service | One service sold to one audience, quote or booking CTA | matrix 3 | seo-content-service-page | service | | location | One physical establishment, NAP, map | matrix 4 | seo-local | location | | comparison | "X vs Y", "alternatives to X", "best X for Y" | matrix 5 | seo-content-comparison-page | comparison | | audience | "for agencies", "for freelancers", one segment, same product | matrix 6 | seo-content-comparison-page (segment section) | audience | | article | Single editorial post, author, date | matrix 7 | seo-content-blog | blog | | homepage | Root URL, whole-offer overview | matrix 8 | seo-content-homepage (copy and block order), `references/transverse-pages.md` (wireframe) | homepage | | pricing | Plans, prices, plan comparison | matrix 9 | this skill, `references/transverse-pages.md` | pricing | | about | Company story, team, proof | matrix 10 | this skill, `references/transverse-pages.md` | abou