SiteBoost — Pilot Bundle (Best Value)

About Will

I run a multi-site content operation on Claude and Notion with autonomous agents — and I write about what we do, including what breaks.

Connect on LinkedIn →

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.

Track the AI tools you actually use
Live, vendor-neutral prices & limits for ChatGPT, Claude, Gemini, Perplexity and more — and we’ll email you the moment your tools change price or limits. Free, no hype.
See the live AI tracker →or set up your alerts

Comments

Leave a Reply

Your email address will not be published. Required fields are marked *