/seo-page-sections

name: seo-page-sections
description: "Find the pages and the on-page sections a site is missing, then write them. Input: a URL (or pasted HTML) and the site archetype. Output: the page types the site should have and does not, then a block-by-block gap report (present, below bar, missing) for each page, plus ready-to-paste content for every gap: FAQ with real buyer questions, breadcrumb, definitions, comparison table, spec table, reviews, trust badges, CTA, cross-links. Covers Shopify, Webflow or WordPress and marketplace archetypes, and 21 page types: product, collection, service, location, comparison, segment, article, blog hub, homepage, pricing, about, contact, call, author, free tool, wall of love, affiliate, 404, listing, login, top 10, plus header and footer rules. Use when a page is technically clean and still underperforms, when someone asks what is missing on their site, when building pages or templates from scratch, or to produce a client-facing checklist of what to add."
license: MIT
metadata:
  author: "Sorank (https://sorank.com)"
  version: "1.0.0"

What is missing on this page

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. This skill compares a page against the reference block list for its type, reports the gaps, 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 page contain the blocks a page of this type must contain". Run this one when the technical layer is already fine and the page still underperforms, or when the deliverable is a build list rather than a diagnosis.

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. Vault structure and protocols: the obsidian-brain skill.

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.

Phase 1: identify the archetype, then the page types

Do this in two 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, and the header, footer and persuasion rules that apply site-wide. Report the page types the site should have and does not 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 | Blueprint owner | |---|---|---| | product | One sellable item, buy box, SKU, Product schema | seo-content-product-page | | collection | A list of products or listings, filters, category URL | seo-content-collection-page | | service | One service sold to one audience, quote or booking CTA | seo-content-service-page | | location | One physical establishment, NAP, map | seo-local | | comparison | "X vs Y", "alternatives to X", "best X for Y" | seo-content-comparison-page | | audience | "for agencies", "for freelancers", one segment, same product | seo-content-comparison-page (segment section) | | article | Single editorial post, author, date | seo-content-blog | | homepage | Root URL, whole-offer overview | references/transverse-pages.md | | pricing | Plans, prices, plan comparison | references/transverse-pages.md | | about | Company story, team, proof | references/transverse-pages.md | | contact | Form, coordinates, hours | references/transverse-pages.md | | blog hub | Index of articles, categories, pagination | references/site-archetypes.md | | call | Booking widget, slot selection | references/site-archetypes.md | | author | One person, bio, list of their posts | references/site-archetypes.md | | free tool | Calculator, generator, checker | references/site-archetypes.md | | wall of love | Aggregated testimonial wall | references/site-archetypes.md | | affiliate | Program terms, commission, signup | references/site-archetypes.md | | 404 | Error page | references/site-archetypes.md | | listing | One marketplace entry | references/site-archetypes.md | | top 10 | Ranked list of options | references/site-archetypes.md | | login | Authentication, and it should be noindex | references/site-archetypes.md |

If a page mixes two types (a service page that also lists products, a homepage that doubles as a pricing page), audit it against both block lists and say so: a merged page usually needs splitting, which is an architecture finding, not a section finding. One intent equals one page.

Phase 2: detect what is actually there

python3 scripts/section_audit.py https://example.com/products/thing
python3 scripts/section_audit.py https://example.com/a https://example.com/b --type comparison

Per page it returns: page type guess, wor