The SEO Methodology
A versioned framework for the technical and on-page layer every page on this site is built against — five pillars, each with an explicit, testable verification method, developed from real full-site audits rather than general SEO advice. Looking for the AI-citation layer instead? Read the AEO Methodology.
Scope & intent
This document defines five pillars a page must satisfy to be considered technically sound SEO under this methodology, plus the specific method used to verify each one. It sits underneath the AEO Methodology rather than replacing it — this is the indexation, metadata, and architecture layer that both classic search ranking and AI citation depend on. Where a claim in this document is empirical rather than definitional, it links to the underlying audit data in the same sentence, per Pillar 2 below applied to itself.
Pillar definitions & verification criteria
Indexation & Crawlability
A page that search engines can't correctly index doesn't rank, no matter how good the content is. Every indexable page needs exactly one canonical URL, needs to actually appear in the sitemap, and needs nothing in robots.txt silently contradicting that.
Pass criteria
- Every indexable page declares a canonical tag pointing to itself, not to a different URL
- sitemap.xml lists every indexable page and nothing that's noindexed or removed
- robots.txt disallows only pages genuinely meant to stay out of search — nothing is blocked by accident
Verification method
Fetch sitemap.xml directly and cross-check a sample of listed URLs against their live canonical tags and robots.txt rules. A full-site canonical audit on this site found and corrected 79 of 178 mismatched canonical tags on first pass.Metadata Discipline
Title tags and meta descriptions are the first thing a search result shows, and they're cheap to get wrong at scale — copy-pasted across pages, run long enough to get truncated, or written once and never re-checked as a site grows.
Pass criteria
- Every <title> is 60 rendered characters or fewer and is unique on the site
- Every meta description is 140–160 rendered characters, front-loaded with the page's core claim
- og:title and og:description are written independently, not copy-pasted from the <title> and meta description
Verification method
Grep the whole site for title and meta description lengths before shipping. A 318-file root sweep on this site corrected 66+ over-length titles and 81 meta descriptions found this way — published on the incident log.Structured Data Completeness
Schema markup only helps if it's actually present, actually valid, and actually matches what a visitor sees on the page. Partial or inconsistent structured data is worse than none, because it can silently fail validation without breaking the visible page.
Pass criteria
- Every indexable content page carries BreadcrumbList JSON-LD, except fictional demo pages built to showcase a blueprint
- Pages with genuine recurring questions carry FAQPage schema phrased the way people actually ask
- Organization, LocalBusiness, and Person schema match the visible on-page text exactly, with no orphaned or contradictory fields
Verification method
Parse each page's JSON-LD blocks independently and validate their position sequences and required fields — don't just grep-count a shared key name across the page, since two schema blocks can share a field name like "position" and mask a bug in one while the other looks fine. As of July 23, 2026, BreadcrumbList is live on 73 pages and FAQPage on 47, both grep-verified against the live site.Architecture & Internal Linking
A page's structure needs to hold up at every viewport and guide both users and crawlers to related content. Heading order that skips levels, tables that force horizontal scroll on mobile, and orphaned pages with no inbound links all quietly work against a site's own SEO.
Pass criteria
- Heading levels never skip (h1 → h2 → h3, no jumping straight to h4)
- No page causes horizontal scrolling at any viewport width; wide tables collapse to a stacked-card pattern below 600px
- Every content page links to and from at least one related page — a blueprint to its research post and Ads guide, a platform benchmark to its before/after pair
Verification method
Walk the heading sequence of each page manually and check for skipped levels; test horizontal scroll on a real narrow viewport, not just desktop devtools resized. The same 318-file sweep that fixed metadata also corrected 19 heading-order violations found this way.Verification & Maintenance Loop
SEO health degrades quietly as a site grows — a count that was accurate at launch goes stale the moment a new page ships, and nobody notices until an outside reader catches it. This has to be checked on a fixed schedule, not only when something already looks broken.
Pass criteria
- Any time a countable thing changes (blog posts, blueprints, platforms), the whole site is grepped for every place that count is hardcoded elsewhere
- A full architectural sweep — titles, meta descriptions, canonicals, heading order, sitemap accuracy — happens on a stated cadence, not only when a problem is suspected
- The cadence is a stated number, not "regularly," and one named person is accountable for running it
Verification method
Run the full sweep every 4 weeks, matching the AEO Methodology's cadence, and publish what changed on the incident log whichever way it lands. Ari Subana owns this cadence and is the single point of accountability for running it and acting on what it finds.Why these five pillars, specifically
This methodology wasn't assembled from a generic SEO checklist — it was built from two real, full-site audits run on this domain: a canonical-tag audit across every published page, and a 318-file root sweep checking titles, meta descriptions, heading order, and sitemap accuracy in one pass.
Every pillar above traces back to one of these two audits: Pillar 1 to the canonical-tag findings, Pillars 2 and 4 directly to the 318-file sweep. Pillar 3's live counts (73 pages with BreadcrumbList, 47 with FAQPage) and Pillar 5's cadence are both re-verified as part of the same recurring sweep going forward, published on the incident log whichever way the numbers land.
Checked by systems outside our control
Grok was asked to grade this site's actual SEO and AEO implementation directly, unedited, published in full. Read Grok's grades.
ChatGPT independently landed on A- (8.8/10) for SEO and A (9.3/10) for AEO from the site's public content alone. Read ChatGPT's grades.
A separate Perplexity conversation, unprompted, checked the site's AEO methodology and cited its real pillar structure, citation-test numbers, and grades accurately — the one gap it found (a vague re-test cadence) has since been fixed in the AEO Methodology itself.
Common questions
What is the SEO Methodology?
It's ZenMasterWorks's formal, versioned framework for technical and on-page SEO — five defined pillars, each with an explicit verification method, developed from real site-wide audits rather than general SEO advice.
How is this different from the AEO Methodology?
The AEO Methodology covers how AI answer engines read and cite a page. This methodology covers the layer underneath it — indexation, metadata, structured data, and site architecture — that AEO and traditional search ranking both depend on. A page can pass this methodology and still fail AEO if it doesn't also demonstrate evidence density and entity clarity.
What evidence supports this methodology?
A 318-file root sweep of this site corrected 66+ over-length titles, 81 meta descriptions, and 19 heading-order violations. A separate canonical audit found and corrected 79 of 178 mismatched canonical tags. Both are published on the incident log.
Is this methodology open to use by other sites?
Yes. The five pillars and their verification criteria are published in full on this page, free to apply to any site. ZenMasterWorks also offers this as a service for businesses that want it implemented and verified directly.
Want this applied and verified on your own site?
We build the page first, run the same indexation, metadata, and structural checks defined above, and you pay only if you're satisfied with the result.
Start a Project →