Tag: WordPress Optimization

  • SiteBoost — Monthly Retainer

    SiteBoost — Monthly Retainer

    $997

    Delivered by email after checkout.

    Buy Now →

    Secure checkout via Square — all major cards accepted

    You can copy this method and run a month of WordPress work yourself. Buy Now is Will doing that month on your site: ten existing-post optimizations and four new articles, already connected.

    SiteBoost Monthly Retainer is a service. Square lists it per month at $997. The /siteboost/ hub defines the month as 10 posts + 4 articles. That is the scope. Not “unlimited blog support.” Not ads. Not a redesign.

    This SKU assumes the site is already connected and you have a baseline. If it is not, run Site Connection and Audit first (or the Pilot, which includes the connection). Self-hosted WordPress only. Posts, not Pages, unless you put a Page in writing.

    What a month includes

    From the public hub, two work types:

    • 10 existing-post optimizations. Same method as the $47 SKU, ten times. SEO, AEO, GEO, schema, interlink, IndexNow. Highest-opportunity published posts, agreed before the month starts if you can, or pulled from the last audit if you already have a queue.
    • 4 new articles. Same method as the $97 SKU, four times. Brief, write, three layers, taxonomy, internal links, publish, IndexNow.

    That is 14 URLs touched in a month if you finish the scope. The pilot is ten existing posts and a 60-day wait. The retainer is the ongoing version: keep refreshing the library and keep adding posts, on a calendar.

    The weekly rhythm

    The operator guide on tygartmedia.com is the calendar. Scope changes. Process does not.

    1. Monday. Audit and pick. Re-pull the inventory or last month’s leftover queue. Score content health. Pick this week’s existing posts and the next new-article brief. Do not start writing until the week’s list is written down.
    2. Tuesday to Thursday. Execute. Existing-post passes and new-article drafts. Every action gets all three layers by default. Schema on every URL you touch. Interlink into the cluster you are building, not random related-posts widgets.
    3. Friday. Verify. Re-read what you published or refreshed. Rich Results Test on the new or changed URLs. IndexNow pings. Log what shipped: URL, what changed, word count, schema types, which brief it came from.

    The 23-site stack article adds the monthly maintenance layer on top of that week: taxonomy health, orphan detection, meta-pollution scan (wp-clean-meta), and a look at rankings / competitor movement if you have Search Console and a research tool. Do that once a month, not every Monday, or you will spend the retainer on reports.

    How to pick the ten and the four

    Existing ten, same rules as the pilot:

    • Impressions but empty meta / no FAQ / no schema.
    • Over 500 words, real query, missing AEO and GEO.
    • Across pillars, not ten from one tag.
    • Skip stubs, test posts, and anything you are about to redirect.

    Four new articles, same rules as New Article Publishing:

    • Start from a brief: keyword, intent, PAA list, sources you can name, internal-link targets that already exist.
    • Prefer spokes that point back to a hub you already optimized, or a hub you will optimize this month. The SiteBoost cluster process is hub and spoke with bidirectional links. A new post that does not link to anything, and is linked from nothing, is a wasted slot.
    • content-quality-gate before publish: no unsourced claims, no fabricated stats.

    A month on a legal pad

    Write these lines on day 1, then fill them as you go:

    1. Site URL. Connection still works? (users/me 200)
    2. This month’s ten existing URLs (before title / after title).
    3. This month’s four briefs (keyword, intent, target publish date).
    4. Monday notes: what the audit still says is on fire.
    5. Friday logs, four of them.
    6. Month-end: Search Console on the 14 URLs versus last month. What you would pick next month. What you would stop.

    If you cannot name the 14 URLs at month-end, you did not run a retainer. You blogged.

    What a month does not include

    • Page redesigns, theme work, or plugin installs.
    • Google Ads, GBP posts, or social, unless you hired those separately.
    • Editing attorney bios, service pages, or the homepage without a written ask.
    • A promised ranking. The public SiteBoost copy measures at 60 days and treats traditional SEO as 60 to 90 days on competitive terms. A single month is a shipping month, not a miracle month.

    How this sits next to the other doors

    Connection and Audit is the one-time setup. Pilot is connection + ten existing posts + a 60-day report, once. Retainer is the monthly machine after that. Existing Post Optimization and New Article Publishing are the à la carte versions of the same two work types if you do not want a month.

    If you want the skill files so your own Claude can run the week, that is the WordPress SEO Skill Pack. Pro has the full refresh stack and the content pipeline. Agency adds new-site setup and thin-content expansion, which is what you need if you are the one retaining other people’s sites.

    If you want Will to run the month

    You can keep the Monday / midweek / Friday rhythm on your own staff. Buy Now is Will doing the month: ten existing-post passes, four new articles, shipped through the REST API, with a log of what changed. Same Square button at the top. $997 per month.

    Email the site URL after checkout. If the site is not connected yet, the first month still needs the Application Password and the baseline. Do not send the login password. Application Password only.

  • SiteBoost — Site Connection & Audit

    SiteBoost — Site Connection & Audit

    $297

    Delivered by email after checkout.

    Buy Now →

    Secure checkout via Square — all major cards accepted

    You can copy this method and connect and audit the site yourself. Buy Now is Will doing the one-time setup: Application Password, REST API check, full inventory, and the baseline reports.

    Site Connection and Audit is a service. Square lists it as a one-time setup at $297. It is the front door for every other SiteBoost SKU. The public vertical pages include it inside the pilot. Alone, it is how a site gets on the board without anyone rewriting a post yet.

    Self-hosted WordPress only. REST API on (the default). Squarespace, Wix, and Webflow are not compatible. The /siteboost/ hub is blunt about that.

    How Will connects a site

    wp-connect is the gateway skill. Nothing else in the WordPress stack runs until this works. The 23-site stack article on tygartmedia.com puts a new site at about 20 minutes: Application Password, registry, first audit.

    1. Confirm the site is self-hosted WordPress. Open /wp-json/wp/v2/ in a browser. You should see a JSON index, not a 404. If the REST API is blocked, stop and fix that before anyone shares a password.
    2. In WordPress, go to Users → Profile (or Users → Application Passwords, depending on version). Create an Application Password for a user who can edit posts. Name it something you will recognize later, like “SiteBoost” or “REST audit.” Copy it once. This is not the login password. wp-connect will not use the login password.
    3. Test the connection. GET https://yoursite.com/wp-json/wp/v2/users/me with HTTP Basic auth, username plus the Application Password. A 200 with your user object means you are in. A 401 means the password or user is wrong. A 403 often means a security plugin is blocking REST for that user.
    4. Confirm you can list posts: GET /wp-json/wp/v2/posts?per_page=1&status=publish. If users/me works but posts 403, the user is missing the edit_posts capability.
    5. Write down: site URL, WordPress version if you can see it, hosting (WP Engine, SiteGround, Flywheel, Kinsta, Cloudflare in front, or other), whether Yoast / Rank Math / AIOSEO is present, and who holds the Application Password. Do not put the password in a public doc.

    The public SiteBoost pages name the hosts they have used this pattern on: WP Engine, Flywheel, SiteGround, Cloudflare-proxied sites, GCP Compute Engine, DigitalOcean, Kinsta, bare metal. The requirement is the REST API, not a specific host.

    Do not install a plugin to “help” the connection. SiteBoost’s rule is no plugins added to the client site. Application Passwords are built into WordPress 5.6 and later.

    What the audit checks

    wp-site-audit is the skill that runs at the start of any new site. Fetch all published posts (per_page=100, walk pages). For each post, score the same fields:

    • Word count. Thin is under 500 words.
    • Title tag and slug quality.
    • Excerpt / meta description present, empty, or polluted (raw JSON or leftover code in the excerpt is a real pattern; wp-clean-meta exists to strip it).
    • Categories and tags. Uncategorized is a fail. wp-taxonomy-fix wants 1 to 2 categories and 5 to 10 tags.
    • Featured image present or not.
    • Internal links in (orphans: nothing points here) and internal links out (dead-end posts).
    • Schema present or not, and which types if you can see them (Article, FAQPage, HowTo, BreadcrumbList, Speakable).
    • FAQ section present or not.
    • Outbound source citations present or not.

    Also roll up site-level numbers: total published posts, total pages (count them, do not edit them), taxonomy health (how many categories, how many unused tags, how many posts still Uncategorized).

    The 60-point WordPress SEO Audit Template on tygartmedia.com is the longer human version of this, in six categories: Technical, On-Page, Content, Schema, Local, Analytics. Tools it wants open: Google Search Console, Bing Webmaster Tools, PageSpeed Insights, your SEO plugin, validator.schema.org, an incognito window. Order matters: Technical first, then On-Page, Content, Schema, Local, Analytics. A quick pass is the high-impact rows. A full pass is a few hours the first time. Re-audit quarterly, and after a redesign, a migration, or a plugin purge.

    SiteBoost’s service audit, as sold, is the content-and-baseline cut of that: inventory, schema gaps, FAQ gaps, before numbers. It is not a Core Web Vitals engagement and it is not a local-pack rebuild. If you want the 60-point sheet as a Notion checklist, that is a different SKU (WordPress SEO Audit Template).

    The four reports you should produce

    The public SiteBoost pages name these deliverables. If you are doing this yourself, write the same four:

    1. Content inventory. One row per published post. URL, title, date, word count, category, meta yes/no, FAQ yes/no, schema yes/no, internal links in/out, notes.
    2. Schema gap report. Which posts have no JSON-LD. Which have plugin-bloated or invalid markup. Priority by page type (Article on posts, FAQPage where a FAQ exists or should, HowTo only on real procedures).
    3. FAQ gap report. Which posts have no Q and A block and no FAQPage schema. Those are the AEO queue.
    4. Before baseline. Search Console coverage and the queries / URLs you will watch. A short note on AI visibility for a handful of real questions in your market (do you show up in Perplexity or an AI Overview today?). Write the date. This is what a 60-day report compares to.

    Priority the way wp-site-audit does: Critical (taxonomy / metadata), High (SEO / AEO / thin content), then optimization (links, expansion). The recommended next skills, if you are running Claude, are wp-taxonomy-fix, wp-content-expand, wp-schema-inject, wp-interlink, then the refresh stack.

    What you do not do in this SKU

    • Do not rewrite posts. That is Existing Post Optimization or the Pilot.
    • Do not publish new articles. That is New Article Publishing.
    • Do not edit Pages, bios, or service templates unless the owner asked in writing. Toolbox rule: posts, not pages.
    • Do not leave the Application Password in chat logs or a public Notion page.
    • Do not claim results. You do not have a after yet. You have a before.

    If you want Will to connect and audit

    You can create the Application Password and fill a spreadsheet this afternoon. Buy Now is Will doing the connection and the four reports, then emailing you the baseline and the recommended ten. Same Square button at the top. $297, one time.

    The Pilot Bundle includes this connection plus ten post optimizations and the 60-day report. The Monthly Retainer assumes the site is already connected. If you only want the skill files so your own Claude can connect and audit, that is the WordPress SEO Skill Pack (Starter has wp-connect, wp-post-fetch, and wp-site-audit).

  • WordPress SEO Skill Pack – Starter

    WordPress SEO Skill Pack – Starter

    $29

    Delivered by email after checkout.

    Buy Now →

    Secure checkout via Square — all major cards accepted

    You can copy this method and do the on-page work yourself in the WordPress editor. Buy Now is the five packaged Claude skill files so your own Claude can connect to the site and run the same steps.

    Starter is the first tier of the WordPress SEO Skill Pack. The live sales page at /wordpress-seo-skills/ lists five skills: wp-connect, wp-post-fetch, wp-site-audit, wp-seo-refresh, wp-clean-meta. $29. It is the connect-and-on-page layer. It is not the AEO, GEO, schema, or interlink stack. Those start at Pro.

    What you need before any skill runs

    • Claude Pro, Max, or Team. The sales page names those tiers.
    • A self-hosted WordPress site with the REST API on.
    • A WordPress Application Password. Users → Profile. Thirty seconds. Not the login password.

    No plugin is required. Everything in this pack talks to /wp-json/wp/v2/.

    If you bought the zip: drop the skill files into Claude Desktop (Cowork) or Claude Code. Then say “connect to my WordPress site” and give the URL, username, and Application Password. The skills ship with placeholders (USER:PASS, SITE). You fill those in. There are no client credentials in the pack.

    The five skills, and the method each one encodes

    1. wp-connect

    Gateway. Must run first. Takes site URL, username, Application Password. Tests GET /wp-json/wp/v2/users/me. Returns whether you are authenticated and which endpoints answered. No other wp- skill works until this is green. If you are doing it by hand, that same curl is the test.

    2. wp-post-fetch

    Load one post so you can see it the way the editor sees it. The refresh skills fetch with context=edit. By hand: GET /wp-json/wp/v2/posts/{id}?context=edit. Read title, slug, excerpt, content, categories, tags. Do not write yet. You cannot refresh what you have not read.

    3. wp-site-audit

    Run this at the start of a site, not after you have already rewritten three posts. Fetch published posts (per_page=100, paginate). For each post, mark:

    • Missing tags, categories, featured image, excerpt / meta
    • Metadata pollution (raw JSON or leftover code in the excerpt)
    • Orphans (no internal links in) and dead-ends (no internal links out)
    • Thin content (under 500 words)
    • Schema present or not
    • Taxonomy health

    Output a prioritized report: Critical (taxonomy / metadata), High (SEO / AEO / quality), then optimization opportunities. That report is your work order. Starter will not auto-fix taxonomy or inject schema. It will tell you which posts are dirty.

    4. wp-clean-meta

    Strip pollution. The 23-site stack article describes this as removing legacy artifacts from excerpts. The audit skill flags raw JSON / code in excerpt fields. Do this before you write a new meta description, or you will be fighting leftover plugin junk. By hand: open the post, clear a garbage excerpt, save a real 140 to 160 character description.

    5. wp-seo-refresh

    The on-page pass. Fetch the post, name the target keyword from the topic, then write:

    1. Title, max about 60 characters, keyword-rich, front-loaded
    2. Meta description, about 155 to 160 characters
    3. Slug: lowercase, hyphenated, keyword-rich (only change it if the current slug is junk)
    4. H2 / H3 hierarchy
    5. Keyword distribution, including the first 100 words
    6. A note of internal-link opportunities (Starter does not run wp-interlink; you place the links yourself or upgrade)

    Then update the post via the REST API and report what changed.

    A Starter session you can run today

    1. Connect. users/me returns 200.
    2. Audit the site. Write the Critical and High lists.
    3. Clean meta on anything the audit marked as polluted.
    4. Pick one High post that is over 500 words. Fetch it. Run the SEO refresh fields above.
    5. Validate the title and meta lengths. Ping IndexNow (Rank Math Instant Indexing, Yoast, or the official IndexNow plugin). Confirm in Bing Webmaster Tools.

    That is the honest Starter method: connect, see the mess, clean the excerpt, fix on-page SEO on one post. Title, slug, meta, headings. Not FAQ schema. Not entity saturation. Not a link graph.

    What Starter does not do

    • No wp-aeo-refresh. No definition box, no 6 to 8 FAQs, no FAQPage schema.
    • No wp-geo-refresh. No speakable / LLMS.txt / named-entity pass as a skill.
    • No wp-schema-inject, wp-interlink, wp-taxonomy-fix, wp-full-refresh, or content pipeline.
    • No new-article factory. You can still write a post by hand using the six-step workflow on the New Article Publishing page.

    If you want those, Pro is the 14-skill stack. Agency adds onboarding and thin-content expansion. If you want Will to do the post instead of running skills, that is SiteBoost Existing Post Optimization.

    If you want the packaged files

    You can keep a checklist and do every Starter step in wp-admin. Buy Now is the five .skill files delivered by email after checkout, genericized, with placeholders for your own site. Same Square button at the top. $29.

    Install, connect, audit, clean, refresh. That is the pack. The sales page’s “full refresh post 123” line (SEO then AEO then GEO then schema then interlink) is the Pro orchestrator, not Starter.

  • WordPress SEO Skill Pack – Agency

    WordPress SEO Skill Pack – Agency

    $149

    Delivered by email after checkout.

    Buy Now →

    Secure checkout via Square — all major cards accepted

    You can copy this method and run it across more than one WordPress site yourself. Buy Now is the 19 packaged Claude skill files plus the three reference guides, so your own Claude can onboard a site, expand thin posts, and run the full stack.

    Agency is the top tier of the WordPress SEO Skill Pack. $149. The live sales page lists 19 skills: everything in Pro, plus an SEO reference guide with schema templates, an AEO reference guide, a GEO reference guide, wp-content-expand, and wp-new-site-setup. The thesis on the launch page: genericized versions of the production wp- skills, no client credentials, placeholders you fill with your own Application Passwords.

    What “agency” means here

    Not a Tygart Media retainer. The pack is for someone who already has (or is about to have) more than one self-hosted WordPress site and wants the same connect → audit → refresh → publish machine on each. The 23-site stack article is the operating picture: one Application Password per site, one audit at the start, skills composed so a full refresh is a named sequence instead of a vibe.

    Requirements stay the same: Claude Pro / Max / Team, REST API on, Application Password, no plugin required. Install the files in Claude Desktop (Cowork) or Claude Code. Connect per site. Do not reuse one app password across clients.

    Onboard a site (wp-new-site-setup)

    The 23-site article times a new site at about 20 minutes: generate the Application Password, add the site to your registry, run the setup / audit skill, and the stack is usable. wp-new-site-setup is that onboarding workflow. By hand, the same steps are:

    1. Confirm /wp-json/wp/v2/ answers. Self-hosted only.
    2. Create an Application Password for an editor-capable user. Label it with the client and the date.
    3. wp-connect. users/me = 200.
    4. wp-site-audit. Full published-post inventory. Critical / High / optimization lists.
    5. Note the SEO plugin (Yoast, Rank Math, AIOSEO) because meta fields differ. A WeConvene audit note in Notion called this out: a skill that only knows Yoast / Rank Math will miss AIOSEO fields.
    6. Write the four baseline artifacts from the SiteBoost audit page: inventory, schema gaps, FAQ gaps, before numbers in Search Console.
    7. Agree the first ten posts or the first briefs before anyone writes. Agency without a queue is just a folder of skills.

    Toolbox rule you should keep: posts, not pages, unless the client put a Page in writing. Do not “clean up” the homepage on day one.

    Expand thin posts (wp-content-expand)

    This is the Agency skill Pro does not have. Never overwrite. Fetch with context=edit. Flag sections under 150 words, intros under 100, missing subtopics, missing examples, outdated stats, missing close. Add 250 to 400 words per new section. Append. Update the modification date because you actually changed the content. Report the word-count increase. The skill’s own bar: get the post over 500 words before you pretend it has SEO authority.

    Then run the Pro refresh stack on the expanded post. Expansion without SEO / AEO / GEO / schema is just a longer stub.

    The Pro stack, still the daily work

    Once a site is onboarded, Agency work is Pro work, repeated:

    • wp-seo-refresh → wp-aeo-refresh → wp-geo-refresh → wp-schema-inject → wp-interlink, or wp-full-refresh to run that chain.
    • wp-taxonomy-fix, including the two-layer category / tag descriptions if archive pages are stubs.
    • content-brief-builder → wp-content-pipeline → content-quality-gate for new articles.
    • wp-clean-meta whenever an excerpt is polluted.

    The three reference guides are the templates sitting next to those skills: SEO (on-page + schema templates), AEO (direct-answer / FAQ / PAA), GEO (entities, density, speakable, citations). Use them as the written standard when more than one person is allowed to run a refresh. If the guide and the skill disagree, the skill’s field list wins for execution; the guide wins for “what good looks like.”

    A week across more than one site

    Same rhythm as the operator guide, scoped to a roster:

    1. Monday: per-site audit score. What is still Critical. This week’s existing posts and this week’s briefs, named by URL and keyword.
    2. Tuesday to Thursday: expand anything under 500 words that you committed to, then full-refresh. New articles through the pipeline and the quality gate.
    3. Friday: Rich Results Test, IndexNow, log. One log line per URL. If you cannot say what changed, it did not ship.

    Monthly, not weekly: taxonomy health, orphan scan, meta-pollution scan, Search Console versus last month. That is the maintenance layer from the 23-site article. Do not burn a week on dashboards.

    IndexNow on every publish and every update. Official plugin or Rank Math / Yoast Instant Indexing. Confirm in Bing Webmaster Tools. Agency volume without a ping is a lot of work the engines have not been told about.

    What this pack is not

    • It is not SiteBoost. SiteBoost is Will (or Tygart Media) doing the work on the site. This pack is the skill files so you can do it.
    • It is not the $297 Connection and Audit service, the $597 pilot, or the $997 retainer. Those are done-for-you doors. The methods on those pages are the same layers. The deliverable is different.
    • It is not a prompt pack of 50 one-liners. The launch page’s distinction: workflows with error handling and a report, genericized from production skills.

    If you only have one site and you only need on-page, Starter is enough. If you have one site and you want the full refresh + pipeline, Pro is enough. Agency is the onboarding + expansion + reference-guide tier.

    If you want the packaged files

    You can run every step in this article with Application Passwords and a checklist. Buy Now is the Agency zip: 19 skills and the three reference guides, delivered by email after checkout, placeholders only, no one else’s credentials. Same Square button at the top. $149.

    If you would rather not run Claude at all, buy the matching SiteBoost service instead of this pack.

  • SiteBoost — Pilot Bundle (Best Value)

    SiteBoost — Pilot Bundle (Best Value)

    $597

    Delivered by email after checkout.

    Buy Now →

    Secure checkout via Square — all major cards accepted

    You can copy this method and run a ten-post pilot yourself. Buy Now is Will connecting the site, picking the ten, running the three-layer pass on each, and sending the 60-day impact report.

    The Square catalog names this SKU “Connection + 10 Posts.” The /siteboost/ hub calls it the best-value door at $597. The public vertical pages (law firms and the rest of the cluster) spell out the same package: Site Connection and Audit, ten existing-post optimizations, and a 60-day impact report. They price the pieces at $767 if you bought them separate ($297 audit + 10 × $47). The bundle is the cheaper way to get a first measured pass.

    What the pilot is, and is not

    It is a retrofit of ten published posts. SEO + AEO + GEO + schema on each. Changes via the WordPress REST API. No plugin left behind. Results looked at around day 60. It is not a retainer, not a redesign, and not ten brand-new articles. New Article Publishing is a different SKU. The monthly retainer is the ongoing door after you like the pilot.

    Self-hosted WordPress only. Squarespace, Wix, and Webflow are out. Posts, not Pages, unless you put a specific Page in writing.

    How to run the pilot yourself

    Week 0. Connect and baseline

    Do the connection and audit first. The method is on the Site Connection and Audit page. Short version:

    1. Create a WordPress Application Password (Users → Profile). Not the login password.
    2. Test GET /wp-json/wp/v2/users/me with that user and app password. If that fails, stop. Nothing else will work.
    3. Pull published posts (per_page=100, paginate if you have more). Inventory every post: title, slug, word count, excerpt/meta, categories, tags, featured image, internal links in, internal links out, schema present or not, FAQ present or not.
    4. Write four artifacts and keep them. Content inventory. Schema gap report. FAQ gap report. Before baseline (the numbers you will compare at day 60: rankings and impressions you can actually see in Search Console, plus a note on AI visibility if you check Perplexity / ChatGPT / AI Overviews on a few queries).

    wp-site-audit’s priority stack: Critical = taxonomy and metadata problems. High = SEO / AEO / content quality. Then link and expansion opportunities. Use that order when you pick the ten.

    Pick the ten

    Highest-opportunity existing articles, with your approval before anyone starts rewriting. That is the rule on the public SiteBoost pages. A practical pick list, from the same audit fields:

    • Posts that already get impressions but have empty meta, no FAQ, and no schema. Those move first.
    • Posts over 500 words that are still missing the AEO and GEO layer. Do not spend the pilot on stubs.
    • Posts that sit on a real query (you can name the keyword). Skip diary posts and leftover test content.
    • A mix across your actual topic pillars, not ten posts from one tag.

    Write the ten URLs down. Get a yes. Then do not swap them mid-pilot unless a post is broken.

    Weeks 1 to 3. Ten existing-post passes

    For each of the ten, run the same method as Existing Post Optimization:

    1. SEO: title 50 to 60, slug, meta 140 to 155, H2/H3, keyword in the first 100 words.
    2. AEO: 40 to 60 word definition box, question H2s with 40 to 60 word answers, 6 to 8 FAQ pairs, FAQPage JSON-LD.
    3. GEO: named entities, sourced facts, speakable blocks, LLMS.txt comment, last-updated + dateModified.
    4. Article schema. Validate. Two to five internal links into the rest of the cluster. IndexNow on the update.

    Sequence on a single post is SEO, then AEO, then GEO, then schema, then interlink. That is wp-full-refresh. Do not GEO a post whose title and meta are still empty.

    If a chosen post is under 500 words, expand it first (append real sections, do not overwrite) or swap it for a thicker post on the same topic. Thin content wastes a slot.

    Day 60. Impact report

    The public pages measure three things: traditional rankings and impressions, People Also Ask / snippet placements, and AI citation visibility. Pull Search Console for the ten URLs (and the queries they were aimed at) versus the before baseline. Recheck the same AI prompts you wrote down in week 0. Do not invent a win. If nothing moved, say so. The report is the point of a pilot. You are deciding whether a retainer is worth it.

    Traditional SEO on competitive terms is often 60 to 90 days. The same pages note that FAQPage / PAA and some AI crawlers can show sooner (they cite 2 to 4 weeks for PAA). Treat those as ranges from the public SiteBoost copy, not a guarantee.

    What you should have on disk at the end

    • Connection notes (site URL, that an app password was created, who holds it).
    • The four audit artifacts from week 0.
    • The list of ten URLs and the before/after for each (title, meta, word count, FAQ count, schema types).
    • The 60-day comparison. What moved, what did not, what you would do next (more existing posts, new articles, or stop).

    If you want Will to run the pilot

    You can do every step above with an Application Password and a spreadsheet. Buy Now is the packaged pilot: Will connects, audits, agrees the ten with you, runs the three layers on each post, and sends the 60-day impact report. Same Square button at the top. $597.

    After a pilot you like, the Monthly Retainer is 10 existing-post passes plus 4 new articles per month. If you only need the connection and the baseline, buy Site Connection and Audit. If you only need one post touched, buy Existing Post Optimization.

  • SiteBoost — Existing Post Optimization

    SiteBoost — Existing Post Optimization

    $47

    Delivered by email after checkout.

    Buy Now →

    Secure checkout via Square — all major cards accepted

    You can copy this method and do it yourself on one published WordPress post. Buy Now is Will running the same three-layer pass on that post and pushing the changes live for you.

    SiteBoost Existing Post Optimization is one post, already on your site. Not a new article. Not a redesign. The public SiteBoost pages call this the post-publish layer: SEO, then AEO, then GEO, written back through the WordPress REST API. No plugin install. Self-hosted WordPress only.

    What you are optimizing

    Pick one published post (post type post, not a Page). Fetch it. Read it as it sits today. Then run three passes in this order. The operator guide on tygartmedia.com is explicit: the layers are concentric, not three separate rewrites. One piece of content. Structure, density, and markup.

    Pass 1. SEO

    This is the foundation. Do not skip it to chase snippets or AI citations. The SiteBoost vertical pages and the wp-seo-refresh skill agree on the same fields:

    1. Title tag. Primary keyword front-loaded. Target 50 to 60 characters. This is the H1 / browser title, not a clever headline that hides the query.
    2. Slug. Lowercase, hyphenated, keyword-rich. Change it only if the current slug is junk. If the post already ranks on the old URL, leave the slug and add a redirect if you must change it.
    3. Meta description. 140 to 155 characters on the SiteBoost sales pages, 155 to 160 in the wp-seo-refresh skill. Write a real sentence a human would click. Empty meta is the most common miss.
    4. Heading structure. Real H2 / H3 hierarchy. No skipped levels. No H2 that is just a label with no answer under it.
    5. Primary keyword in the first 100 words.
    6. Note internal link opportunities. You will place them after the GEO pass, not while you are still rewriting the title.

    Workflow from wp-seo-refresh: fetch the post with context=edit, analyze current on-page SEO, name the target keyword from the actual topic, generate the new title / meta / headings, write the post back, then report what changed.

    Pass 2. AEO

    Answer Engine Optimization. Same post. Restructure so a featured snippet or a People Also Ask box can lift a clean answer.

    1. Add a 40 to 60 word definition box near the top. One sentence that answers “what is this?” without a wind-up.
    2. Turn implied questions into H2s. Under each H2, put a 40 to 60 word direct answer, then the depth.
    3. Add 6 to 8 FAQ pairs that match real People Also Ask questions for the topic. The older WordPress Publish skill used 3 to 5. The SiteBoost vertical pages use 6 to 8. Use 6 to 8 on a SiteBoost-style pass.
    4. Add FAQPage JSON-LD for those pairs. Question and acceptedAnswer. Valid markup, not a plugin dump.

    wp-aeo-refresh also looks for list-shaped answers and natural-language replies a voice result can read. If a section is a process, a numbered list beats a paragraph.

    Pass 3. GEO

    Generative Engine Optimization. Make the post citable by ChatGPT, Perplexity, Claude, Gemini, and Google AI Overviews.

    1. Entity saturation. Name the real organizations, standards, statutes, places, and tools the topic depends on. Entity density, not keyword stuffing.
    2. Factual density. Replace “many companies” and “studies show” with a named source and a number you can actually point to. If you cannot name the source, cut the claim. The citing-sources article on tygartmedia.com is the rule: name the organization in the text, link the primary source, put a sources list at the bottom.
    3. Speakable blocks. Short, self-contained sentences an AI or a voice assistant can lift without the rest of the page.
    4. LLMS.txt as an HTML comment. A seed paragraph the page can carry for LLM citation signals. SiteBoost content standards put this on every page.
    5. Visible last-updated date near the byline, and dateModified in Article schema that matches a real edit. Do not bump the date without changing the content.

    wp-geo-refresh also asks for context richness (define the term, do not just mention it) and semantic clarity (connect related concepts in the same section).

    Schema and IndexNow

    After the three passes, the post should carry Article JSON-LD (headline, author, publisher, datePublished, dateModified) plus FAQPage. BreadcrumbList if the theme does not already emit it. Validate with Google’s Rich Results Test before you walk away. The schema injection sprint on tygartmedia.com is the same rule: pick the type the content actually is, inject JSON-LD, validate, fix failures.

    Then tell the engines the URL changed. IndexNow: official WordPress plugin, or the IndexNow / Instant Indexing toggle in Rank Math or Yoast. Confirm the ping in Bing Webmaster Tools. A publish or an update that nobody recrawls is a pass you did for yourself.

    What you do not touch

    Posts, not Pages. SiteBoost does not rewrite service pages, bios, or the homepage unless someone asked in writing. Do not install a plugin to do this. Do not empty the excerpt into raw JSON. If the excerpt is polluted, strip it (that is the wp-clean-meta job) and write a real meta description.

    A honest one-post checklist

    1. Current title, slug, meta, word count, FAQ count, schema present or not. Write those six lines down. That is your before.
    2. SEO pass. Title, slug, meta, headings, first 100 words.
    3. AEO pass. Definition box, question H2s, 6 to 8 FAQs, FAQPage schema.
    4. GEO pass. Named entities, sourced facts, speakable lines, LLMS.txt comment, last-updated + dateModified.
    5. Two to five internal links to related posts on the same site, descriptive anchors, plus one or two outbound links to primary sources.
    6. Validate schema. Ping IndexNow. Write the after: new title, new meta, new word count, FAQ count, schema types.

    If the post is under 500 words, expand it before you call the SEO pass done. wp-content-expand’s rule: find H2s under 150 words, add 250 to 400 words of real section, append, do not overwrite. Thin posts do not earn the AEO or GEO layer.

    If you want Will to do this post

    You can run the three passes in the block editor this afternoon. Buy Now is the packaged, done-for-you version: Will connects, refreshes that one existing post through the REST API, and emails you what changed. Same Square button at the top of this page. $47 per post.

    If you have ten posts that all need this, the Pilot Bundle is the volume door. If you do not have a connection or a baseline yet, start with Site Connection and Audit. This SKU assumes the post already exists and you already know which one.

  • WordPress AEO/GEO Sprint — Featured Snippets and AI Citation Optimization

    WordPress AEO/GEO Sprint — Featured Snippets and AI Citation Optimization

    Tygart Media // AEO & AI Search
    SCANNING
    CH 03
    · Answer Engine Intelligence
    · Filed by Will Tygart

    What Is an AEO/GEO Sprint?
    An AEO (Answer Engine Optimization) and GEO (Generative Engine Optimization) Sprint is a structured retrofit of your existing WordPress content — restructuring posts so search engines surface them as direct answers, and AI systems cite them in generated responses. Not new content. Not a redesign. Your existing posts, optimized to win in a search landscape that now includes ChatGPT, Perplexity, and Google AI Overviews.

    Google’s search results page looks different than it did 18 months ago. AI Overviews now appear above the organic results. Perplexity cites specific pages instead of ranking a list. ChatGPT recommends sites it’s been trained to recognize as authoritative.

    If your existing content wasn’t built to answer questions directly, it won’t show up in any of those placements — regardless of how well it ranks for traditional SEO.

    We’ve applied this exact retrofit to over 500 posts across restoration, lending, flooring, SaaS, healthcare, and entertainment verticals. We know what changes produce featured snippet captures, what entity patterns make AI systems cite a page, and which schema structures Google’s rich results tool actually validates.

    Who This Is For

    WordPress site owners and operators with existing published content — at least 20 posts — who aren’t appearing in AI-generated answers or featured snippet placements. If you’ve been publishing consistently but not converting that content into search placements that existed 18 months ago, this sprint directly addresses that gap.

    What the Sprint Covers (Per Post)

    • Definition box insertion — 40–60 word direct answer block at the top of the post, formatted for featured snippet capture
    • Question-led H2 restructure — Key headings rewritten as questions with direct answers in the first 50 words following each heading
    • FAQPage section — 5–8 Q&As written for People Also Ask placement, with FAQPage JSON-LD schema
    • Speakable schema blocks — Key paragraphs marked with speakable schema for voice search and AI synthesis
    • Entity saturation pass — Named entities (organizations, certifications, standards bodies, locations) identified and injected throughout
    • External citation injection — 3–5 authoritative source references added per post
    • Article + BreadcrumbList schema — Complete JSON-LD block appended to each post
    • LLMS.TXT comment block — AI-readable seed paragraph added as HTML comment for LLM citation signals

    Sprint Packages

    Package Posts Covered Turnaround
    Starter Sprint 10 posts 5 business days
    Standard Sprint 25 posts 10 business days
    Full Site Sprint 50 posts 15 business days

    Posts are selected collaboratively — we prioritize by traffic volume, keyword proximity to featured snippet triggers, and entity coverage gaps.

    What You Get vs. DIY vs. Generic SEO Agency

    Tygart Media Sprint DIY Generic SEO Agency
    FAQPage JSON-LD schema on every post ✅ Maybe Sometimes
    AI citation signals (LLMS.TXT, speakable) ✅ ❌ ❌
    Entity saturation for niche-specific bodies ✅ ❌ Rarely
    Direct publish to WordPress via REST API ✅ N/A You review drafts
    Validated with Google Rich Results Test ✅ Maybe Sometimes
    Proven in AI-heavy verticals ✅ ❌ ❌

    Ready to Get Your Existing Content Into AI-Generated Answers?

    Send your site URL and a rough post count. We’ll identify your best 10 candidates for AEO/GEO retrofit and quote the sprint that makes sense.

    → will@tygartmedia.com

    Email only. No sales call required. No commitment to reply.

    Frequently Asked Questions

    Will this change my existing post content significantly?

    We add structured elements (definition boxes, FAQ sections, schema) and restructure key headings — we don’t rewrite the body of your posts. Your voice and factual content remain intact. All changes are reviewed before publish if requested.

    How quickly will I see results in featured snippets or AI answers?

    Google typically re-crawls optimized pages within 2–6 weeks for established sites. Featured snippet captures often appear within the first crawl cycle post-optimization. AI citation signals (Perplexity, ChatGPT) are slower — typically 1–3 months for recognition.

    Which verticals have you run this in?

    Property damage restoration, luxury asset lending, commercial flooring, B2B SaaS, healthcare services, comedy and entertainment streaming, and event technology. The entity patterns differ by vertical — we adapt the sprint to the specific certification bodies, standards organizations, and named entities that matter in your niche.

    Do I need to give you WordPress admin access?

    We use WordPress Application Passwords — a scoped credential that doesn’t expose your admin password. You create it, share it, and revoke it after the sprint. We publish directly via WordPress REST API.

    What if my site uses Elementor or another page builder on posts?

    We specifically target WordPress posts (not pages) via the REST API content field — Elementor and page builder data on pages is never touched. This is a hard operational rule we enforce on every sprint.

    Can I pick which posts get the sprint treatment?

    Yes. We provide a prioritized recommendation list, but you make the final call on which posts are included.

    Last updated: April 2026

  • The Addiction Treatment Center WordPress Post-Publish Checklist (8 Steps for Behavioral Health YMYL Content)

    The Addiction Treatment Center WordPress Post-Publish Checklist (8 Steps for Behavioral Health YMYL Content)


    Tygart Media — Behavioral Health Content Strategy

    The Addiction Treatment Center WordPress Post-Publish Checklist (8 Steps for Behavioral Health YMYL Content)

    By Tygart Media Updated: April 12, 2026
    Scope — editorial content only:
    Every step in this checklist applies to educational blog articles — treatment explainers, insurance guides, ASAM level content, family resource articles. None of these steps modify clinical content, admissions claims, treatment outcome descriptions, or patient-facing statements written by your licensed clinical staff. Clinical content integrity is preserved throughout. If you or someone you know needs help, SAMHSA’s National Helpline is available 24/7 at 1-800-662-4357 (free, confidential).
    Why post-publish optimization matters for treatment content: Behavioral health articles are written under clinical standards — accuracy, appropriate language, compassionate framing. But the optimization infrastructure that determines whether a family in crisis finds that article — schema, entity references, authorship markup, FAQPage — is almost never applied after publication. These 8 steps apply that infrastructure to existing articles without altering a single clinical statement, giving your educational content the technical foundation to be found, trusted, and cited.

    The 8-Step Addiction Treatment WordPress Post-Publish Checklist

    1. Rewrite the title tag for family and individual search intent — Match how families and individuals actually phrase their searches, not how clinicians would title a treatment summary. “IOP Program Information” → “What Is an Intensive Outpatient Program (IOP) and Is It Right for You?” Lead with the question framing, stay within 50–60 characters, and reflect the searcher’s perspective — someone evaluating options, not a clinician documenting a level of care.
    2. Write a meta description that is empathetic and informative — Delete the auto-generated excerpt. Write 140–155 characters that acknowledge the family’s situation and promise a specific, useful answer: “Wondering if IOP is the right level of care for your loved one? We explain ASAM Level 2.1 criteria, what a typical week looks like, and how insurance typically covers it.” Empathy first, information second, contact opportunity third.
    3. Add licensed clinician authorship with credential schema — Attribute the post to a named licensed clinician with role, credential (LCSW, CADC, MD/DO, PMHNP), and a link to their bio page. Add a “Medically reviewed by [Name], [Credential]” line with the review date. Implement Article schema with the clinician as named author. This is the highest-impact single action for YMYL behavioral health content — transforming anonymous treatment content into verifiable clinical expertise.
    4. Inject named clinical entity references — Add 3–5 named entities relevant to the article: SAMHSA for any prevalence or treatment standard references, ASAM Criteria level number for any level-of-care descriptions, CARF or Joint Commission as named accreditation authorities, DSM-5 for any diagnostic criterion references, and MHPAEA for any insurance coverage content. These named entities are machine-verifiable — the primary signal Google’s quality evaluators and AI systems use to assess behavioral health content credibility.
    5. Add a family-focused FAQ section with FAQPage schema — Write 6–8 questions in the language families and individuals use during treatment research: “Does insurance cover this level of care?”, “How long does this program take?”, “What happens during intake?”, “What is the difference between [this level] and [adjacent level]?”, “Can my family member work during this program?” Add FAQPage JSON-LD schema alongside the visible FAQ section — both are required for People Also Ask eligibility and AI Overview citation.
    6. Add MedicalOrganization schema connecting the article to the treatment center — Inject Article schema with the facility as publisher and MedicalOrganization schema with named accreditation references (CARF International accreditation scope, Joint Commission certification status), licensed services (SAMHSA-certified facility status if applicable), and staff credential framework. This machine-readable entity connection is what AI systems use to associate clinical authority with a specific verified treatment provider.
    7. Set a visible Last Updated date with dateModified schema — Add “Last reviewed by [Clinician Name], [Credential] on [Date]” near the author byline. Update the dateModified field in Article JSON-LD schema. Treatment guidelines, MAT prescribing protocols, insurance coverage requirements, and ASAM Criteria references change. Outdated behavioral health content on life-impacting decisions is both a YMYL compliance issue and a family trust issue. Visible clinical review dates with schema signal ongoing editorial stewardship.
    8. Add internal links to admissions resources and related treatment content — Link from the educational article to the relevant admissions page, insurance verification page, or program inquiry form — with specific anchor text that connects the educational content to the next step: “Ready to learn if this program is right for your situation? Start the admissions conversation.” Then update the admissions page to link back to relevant educational content. Bidirectional internal linking guides families through the research-to-admissions journey and signals topical depth to Google’s content quality evaluation.
    These 8 steps applied to your 10 highest-traffic behavioral health educational articles is the scope of WordPress content optimization for addiction treatment centers through SiteBoost. Every step pushed live via WordPress REST API — clinical content unchanged, optimization infrastructure added.

    Frequently Asked Questions

    Which of the 8 steps has the highest impact for treatment center content?

    Step 3 (clinician authorship with credential schema) has the highest single-step impact for YMYL behavioral health content — Google’s quality evaluators specifically flag anonymous treatment content as a trust deficiency. Steps 4 and 5 (entity injection and FAQPage schema) produce the fastest measurable results: SAMHSA/ASAM entity references improve AI citation probability within weeks, and FAQPage schema enables People Also Ask placement eligibility within 2–4 weeks for the family research questions that precede admissions calls. All 8 together create compounding returns that no individual step achieves alone.

    Should these steps be applied to all treatment articles or prioritized?

    Prioritize by treatment content category importance and existing traffic. Start with your highest-traffic articles in your primary service categories: insurance and benefits verification content (highest conversion driver), ASAM level-of-care explainers (highest family research volume), and “how to help a loved one” family guidance content (highest pre-decision traffic). Apply all 8 steps to these high-priority articles first. New educational content should have all 8 steps applied at publication — establishing the optimization standard from the point of creation rather than retroactively.

    Does this optimization approach comply with HIPAA and LegitScript requirements?

    Yes. All 8 steps apply to publicly published editorial blog content — no patient data, no protected health information, no admissions-specific identifiers. HIPAA governs patient data collection, storage, and transmission — not publicly published educational content about treatment options. LegitScript certification governs paid advertising eligibility — not organic educational content on a treatment center’s website. The schema markup, entity references, and structural optimization described here are standard web publishing practices that do not create HIPAA or LegitScript compliance concerns.

    Sources: SEO Tuners, “Rehab SEO Guide for Addiction Treatment Centers 2026”; Webserv, “Treatment Center SEO Guide: Increase Admissions 2026”; Knack Media, “SEO for Addiction Treatment Centers: The Definitive E-E-A-T Guide” (November 2025); SAMHSA — samhsa.gov; Google Search Quality Rater Guidelines (2024 edition)
  • Why Addiction Treatment Center Blog Posts Don’t Drive Admissions (And the 4 Fixes That Change That)

    Why Addiction Treatment Center Blog Posts Don’t Drive Admissions (And the 4 Fixes That Change That)


    Tygart Media — Behavioral Health Content Strategy

    Why Addiction Treatment Center Blog Posts Don’t Drive Admissions (And the 4 Fixes That Change That)

    By Tygart Media Updated: April 12, 2026
    A note on this content:
    This article addresses WordPress content optimization for addiction treatment center websites — specifically the structural and schema optimization gaps that prevent educational content from reaching families in crisis. All optimization discussed here applies to editorial blog content only. We never modify clinical content, admissions claims, or patient-facing statements. If you or someone you know needs help, SAMHSA’s National Helpline is available 24/7 at 1-800-662-4357.
    The treatment center content gap: According to SAMHSA’s 2025 National Survey, 46.3 million Americans aged 12+ met criteria for a substance use disorder in 2024 — yet only 24% received treatment. Among the barriers: families cannot find trustworthy, accessible treatment information when they search. Most treatment center WordPress blogs publish educational content that never surfaces in Google search or AI assistants, not because it’s inaccurate, but because it lacks the four optimization signals that determine whether Google’s YMYL evaluation treats it as credible — and whether families find it during the critical hours before they make a call.

    Why Treatment Center Content Faces the Highest Standard in SEO

    Addiction treatment content is classified by Google as YMYL — Your Money or Your Life — at its highest sensitivity level. This means Google’s quality evaluators specifically assess whether addiction content is authored by licensed clinical professionals, whether treatment descriptions cite named standards bodies (SAMHSA, ASAM, CARF, The Joint Commission), and whether the content serves the family and individual in crisis rather than simply marketing a facility. The treatment center that meets these standards earns both Google trust and family trust at the same time.

    Why don’t addiction treatment center blog posts drive admissions despite regular publishing?
    Addiction treatment center blog posts fail to drive admissions when they lack four signals Google’s YMYL evaluation requires for behavioral health content: licensed clinician authorship with verifiable credentials and a linked bio page, named clinical entity references (SAMHSA, ASAM levels of care, CARF or Joint Commission accreditation, specific treatment modalities like MAT or DBT), FAQPage JSON-LD schema targeting the admissions research questions families ask during a crisis, and a visible Last Updated date with dateModified Article schema that signals content currency. Without these signals, the article cannot compete with national treatment directories or receive AI citation during family crisis searches.

    Fix 1: Licensed Clinician Authorship With Credential Schema

    Every addiction treatment blog post must be attributed to or reviewed by a named licensed clinician — not “treatment team” or “editorial staff.” The standard per SEO Tuners’ 2026 rehab SEO guide: an author box near the top of each page with name, role, credential, and service focus, plus a medical reviewer name, credential, and review date. This author attribution should be implemented in Article schema markup with the clinician’s credential properties — turning the visible byline into a machine-readable expertise signal that Google’s quality evaluators can verify.

    Fix 2: Named Clinical Entity References

    Treatment content authority comes from naming the specific standards and bodies that govern the field. An article about IOP (Intensive Outpatient Program) that references “ASAM Level 2.1 — Intensive Outpatient Services,” cites “SAMHSA’s Treatment Improvement Protocol (TIP) 47 on substance abuse intensive outpatient treatment,” and notes “CARF International accreditation standards for behavioral health programs” signals clinical precision that families can trust and AI systems can verify. These are the entity anchors that separate authoritative treatment content from facility marketing copy.

    Fix 3: FAQPage Schema Targeting Admissions Research Questions

    Families researching treatment ask specific, urgent questions before they call an admissions line: “Does insurance cover addiction treatment?”, “What is the difference between inpatient and outpatient rehab?”, “How long does drug detox take?”, “What is MAT treatment?”, “What should I expect during intake?” A FAQ section with 6–8 of these questions structured as direct answers, with FAQPage JSON-LD schema, positions your content for People Also Ask placements that appear above organic results for these crisis-driven queries — capturing family attention before they find a national directory.

    Fix 4: Visible Last Updated Date With dateModified Schema

    Treatment guidelines, insurance coverage rules, and medication protocols change. A 2022 article about MAT (Medication-Assisted Treatment) using outdated buprenorphine prescribing information is a liability for both patient safety and YMYL compliance. A visible “Last updated: [date]” near the author byline and a dateModified field in Article JSON-LD signal ongoing clinical editorial stewardship — that the facility is maintaining its educational content as a genuine resource, not abandoning it after publication.

    All four fixes — clinician credential schema, SAMHSA/ASAM entity injection, FAQPage schema, and dateModified implementation — are part of WordPress content optimization for addiction treatment centers through SiteBoost. Editorial blog content only; clinical content unchanged.

    Frequently Asked Questions

    What types of addiction treatment content generate the most admissions inquiries?

    Insurance and coverage content generates the highest admissions inquiry rate — “does insurance cover addiction treatment,” “what is benefits verification,” “how do I use my insurance for rehab” — because financial barriers are the most common reason families delay seeking treatment. Process content (“what happens during detox,” “what is an IOP program,” “what should I expect during intake”) converts families who have decided to seek treatment and are choosing a facility. Both content types benefit from FAQPage schema targeting the specific questions families ask before calling, and from clinician authorship schema that signals clinical trustworthiness.

    Should addiction treatment content be written by clinicians or content writers?

    RxMedia’s 2026 behavioral health marketing guide recommends blog posts written or reviewed by licensed clinicians — with the authorship and review clearly attributed. The optimal process: a licensed clinician (LCSW, CADC, MD/DO, PMHNP) provides clinical input, key points, and review of factual accuracy; a writer structures and publishes the content; the clinician is attributed as the author or medical reviewer with a linked bio and credential schema. Pure content-writer-only behavioral health content, without any clinical review or attribution, increasingly triggers YMYL compliance penalties under Google’s 2025 quality evaluation standards.

    How does LegitScript certification affect treatment center content optimization?

    LegitScript certification governs paid advertising eligibility — Google Ads, Facebook Ads — for addiction treatment facilities. It does not directly affect organic SEO or content optimization. SiteBoost optimizes editorial blog content only — educational articles, treatment explainers, insurance guides — not paid advertising landing pages or PPC-specific conversion content. The editorial content optimization described here is fully compatible with LegitScript certification requirements and does not add marketing claims, guarantee language, or solicitation content that would create compliance concerns.

    Sources: SAMHSA 2025 National Survey on Drug Use and Health; SEO Tuners, “Rehab SEO Guide for Addiction Treatment Centers 2026”; RxMedia, “How to Build a Comprehensive Addiction Treatment Marketing Strategy Through SEO” (March 2026); Webserv, “Treatment Center SEO Guide: Increase Admissions 2026”
  • The Insurance Agency WordPress Post-Publish Checklist: 7 Steps Every Coverage Article Needs

    The Insurance Agency WordPress Post-Publish Checklist: 7 Steps Every Coverage Article Needs


    Tygart Media — Insurance Content Strategy

    The Insurance Agency WordPress Post-Publish Checklist: 7 Steps Every Coverage Article Needs

    By Tygart Media Updated: April 12, 2026
    Why post-publish optimization matters for insurance content: Insurance blog posts are written with coverage accuracy as the primary concern — which is correct. But the optimization signals that determine whether a prospect finds that article — title tag, meta description, entity references, schema, FAQ section — are almost never applied after publication. These 7 steps apply those signals to existing articles without altering coverage content, converting published articles into AI-citable, PAA-eligible, quote-driving assets.

    The 7-Step Insurance WordPress Post-Publish Checklist

    1. Rewrite the title tag for how prospects ask coverage questions — Match prospect language, not agent vocabulary. “Commercial General Liability Coverage Overview” → “What Does General Liability Insurance Cover for My Business?” Lead with the prospect’s question framing within 50–60 characters. For comparison articles: “Term vs. Whole Life Insurance: Which Is Right for You?” beats “Term and Whole Life Insurance Comparison.”
    2. Write a meta description targeting the pre-quote research moment — Delete the auto-generated excerpt. Write 140–155 characters that speak directly to the prospect’s coverage question and signal authoritative answers: “Wondering what general liability covers for your business? We explain ISO CG 00 01 policy coverage, common exclusions, and typical cost ranges. Get a free quote.” This converts impressions to clicks by promising a specific, credible answer.
    3. Inject named insurance entity references into the content — Add 3–5 named regulatory and standards entities relevant to the coverage type: ISO policy form number, NAIC regulatory reference, AM Best carrier rating mention, and any applicable federal program (NFIP, ACA, ERISA). These named entities are machine-verifiable — the specific signal Google YMYL quality evaluators and AI systems use to distinguish genuine insurance expertise from generic coverage summaries.
    4. Add a coverage FAQ section with FAQPage schema — Write 6–8 questions in prospect language targeting the pre-quote research phase: “How much does [coverage type] cost?”, “What doesn’t [coverage] cover?”, “Do I need [coverage type]?”, “What is the difference between [option A] and [option B]?” Add FAQPage JSON-LD schema alongside the visible FAQ section — both are required for People Also Ask eligibility and AI Overview citation.
    5. Add InsuranceAgency schema connecting content to the agency entity — Inject Article schema with the licensed agent or agency as author and InsuranceAgency schema connecting the content to the specific agency entity (name, license number where appropriate, state of licensure, lines of authority). This machine-readable entity connection is what AI systems use to associate coverage authority with a specific licensed agency — turning content citations into agency brand recognition.
    6. Set a visible Last Updated date with dateModified Article schema — Add “Last updated: [Quarter, Year]” near the article top. Update the dateModified field in Article JSON-LD schema. Insurance coverage terms, pricing factors, and regulatory requirements change. A 2022 article about ACA marketplace coverage is outdated for 2026 prospects. The visible update date signals that the coverage information is current — a critical trust signal for YMYL insurance content that directly influences financial protection decisions.
    7. Add an inline quote CTA in the article body — Embed a quote request CTA in the article content — not just in the header or footer. Prospects who landed directly on the article via search or AI citation are reading the article, not navigating the website. “Ready to find out what [coverage type] costs for your situation? Get a free, no-obligation quote from our licensed agents.” Position this CTA after the FAQ section — at the moment of highest trust and lowest resistance.
    These 7 steps applied to your 10 highest-traffic insurance coverage articles is the scope of WordPress content optimization for insurance agencies through SiteBoost. Every step pushed live via WordPress REST API — coverage content unchanged, optimization and citation infrastructure added.

    Frequently Asked Questions

    Which of the 7 steps has the highest impact for insurance agency content?

    Step 3 (named entity injection — NAIC, ISO, AM Best) and step 4 (FAQPage schema) produce the fastest visible results for insurance content. Named entity references create the YMYL authority signals that Google quality evaluators specifically look for in insurance content, and FAQPage schema enables People Also Ask placement within 2–4 weeks. Step 7 (inline quote CTA) has the highest direct revenue impact — converting article readers who were already engaged by the content into active quote requests. All 7 together create compounding returns that no individual step achieves alone.

    Should these steps be applied to all insurance articles or prioritized?

    Prioritize by coverage line importance and existing traffic. Start with your highest-traffic articles in your primary lines of authority. For a personal lines agency: homeowners, auto, umbrella, and life content first. For a commercial lines agency: BOP, CGL, professional liability, and commercial auto first. Apply all 7 steps to these high-priority articles, then systematically work through secondary content. New articles should have all 7 steps applied at publication — not retroactively — establishing the optimization standard from the point of creation.

    Do these steps require any special WordPress setup or developer access?

    No special setup or developer access is required. Title tags and meta descriptions are managed through post fields or SEO plugin meta fields. Entity references and FAQ sections are text and HTML additions to existing post content. FAQPage, InsuranceAgency, and Article JSON-LD schema blocks are added as HTML blocks in post content via the WordPress REST API. InsuranceAgency schema requires only the agency’s name, license number, and state — publicly available information that agents can provide. The WordPress Application Password required for REST API access is generated from the WordPress admin dashboard in under a minute.

    Sources: Nationwide Agency Forward, “Benefits of SEO, GEO and AEO for Insurance Agents” (InsuranceAgency schema reference); Amsive, “Answer Engine Optimization” (conversion rate data); Marketing LTB, “10 Best Insurance SEO Agencies in 2026” (YMYL compliance section); ClickGiant, “AEO for Insurance Agencies: How to Get Found in AI Search 2026”