Why this matters for an insurance agent
For the agent, this consistency is what makes the results real and repeatable. Following the standard every time means every agent we onboard gets pages that actually rank and honest expectations they can trust. That is what earns renewals and referrals, and it is what keeps the agent recommending us to the next agent.
Run the standard, in sequence
Every client site or page follows the same layered SEO standard, in this order. Do not skip a layer.
Structure first
Design the page set: unique value per page, hub-and-spoke internal links, breadcrumbs, no thin or duplicate content, no keyword cannibalization. Use this whenever we build pages at scale (location or service pages).
Technical SEO while building
Correct meta tags, canonical, JSON-LD, sitemap, robots, mobile. Bake it in so every page is right by default, not fixed later.
AI readiness alongside
Self-contained first-paragraph answers, connected schema, real FAQ, AI crawlers allowed. Make pages extractable by AI search.
Design and responsiveness
Accessible contrast (4.5:1), 44 by 44 px touch targets, focus rings, clean typography, mobile-first adaptive layout. No emoji as icons.
Verify last
Run the audit against the output. Fix every Critical and High finding in the source, not just report them. Then, and only then, it is done.
Non-negotiables on every page
- Unique keyworded title (50 to 60 chars) and unique description (150 to 160 chars). No em dashes.
- Exactly one keyworded H1, then logical H2/H3.
- Self-referencing canonical to the final production URL, and index,follow on indexable pages.
- Full connected @graph LocalBusiness/InsuranceAgency JSON-LD (not a bare stub), plus WebPage, Service, FAQPage, BreadcrumbList.
- Complete Open Graph and Twitter tags including og:image with width, height, and alt.
- Descriptive alt text on all real images.
- The page returns 200, is indexable, and is listed in the sitemap (money and ranking pages only).
Do this, never that
+ Always
- Use only the client's real review data
- Keep NAP byte-consistent across site, GBP, and citations
- Allow AI crawlers (block only training-only CCBot)
- 301-redirect every old URL on a takeover, keep the domain
- Deploy through the central queue, never touch AWS directly
- Revert any staging noindex before launch
x Never
- Fabricate aggregateRating, star counts, or reviews
- Ship a staging noindex or Disallow: / to production
- Use em dashes in any copy
- Keyword-stuff a business name or a page
- Duplicate location pages by swapping only the city
- Promise guaranteed AI or Google top rankings
Honesty is the brand
Readiness is the cause we deliver; rankings and AI mentions are effects we optimize for and measure, not guarantee. "Top 3 in Google" is satisfied by the map pack or the organic links, never a promise of a specific surface. A going-in read is directional. Real determination comes after we have Search Console and Google Business Profile access. Set expectations this way with every client, every time.
You are ready
You now have the model, the vocabulary, and the rules. Run the standard in order, respect the guardrails, and when in doubt, ask before you ship. That is the whole job.
* Key takeaways
- Every build follows the layered standard in order: structure, technical SEO, AI readiness, design/responsive, then verify.
- Fix every Critical and High audit finding in the source before calling a build done.
- Per-page baseline: unique title and description, one H1, canonical, connected @graph schema, full OG tags, alt text, indexable and in sitemap.
- Always: real reviews only, consistent NAP, allow AI crawlers, 301s and same domain on takeovers, deploy through the queue.
- Never: fake reviews, staging noindex to prod, em dashes, keyword stuffing, token-swapped city pages, guaranteed-ranking promises.
- We promise readiness and measurement, never guaranteed rankings. Top 3 can mean the map pack or organic, not a specific surface.
Module 10 quiz
Score 75% or higher to complete this module and unlock the next one.
6 questions
Not completed-
What is the correct order of the build standard?
Why: Structure, then technical SEO, then AI readiness, then design and responsiveness, and verify last.
-
During the verification step, what do we do with Critical and High findings?
Why: We fix every Critical and High finding in the source, not just report them, before calling the work complete.
-
Which is a hard never?
Why: A staging noindex or Disallow: / in production hides the site from search. It must never reach production.
-
A client asks us to guarantee number one on Google. What is the right response?
Why: We deliver readiness and measurement. Rankings and AI mentions are optimized and measured, never guaranteed.
-
How do we publish a finished client site?
Why: All deploys go through the central queue so sessions never conflict. We never touch AWS directly.
-
"Top 3 in Google" is honestly satisfied by:
Why: Top 3 can be earned in either the map pack or organic results. We never promise a specific surface.