Sample audit · chappiethebot.com · 2026-05-13

A real audit of our own site.

Below is the actual SEO audit we ran on chappiethebot.com, our sister site. Findings are real. The recommendations are what we’d ship. We figured the cheapest way to show what your free audit looks like was to publish ours.

The money table

Top 5 fixes ranked by impact-per-hour. Owner, evidence, ship in.

Fix	Impact	Hours
Add /robots.txt + /sitemap.xml	Indexability — pages can be missed by Google	0.5h
Add JSON-LD Organization + WebSite schema	Rich results — sitelinks, knowledge panel eligibility	1h
Add per-route canonical URL	Prevent duplicate-content ambiguity (e.g., /chase vs /chase/)	0.5h
Add structured FAQ schema on /chase	Rich results — FAQ accordions in SERP	1h
Submit to GSC + verify property	Performance data, indexing requests, manual actions visibility	0.25h

Total: ~3.25 hours of focused work to hit all five.

01 · Quick wins (ship this week)

No /robots.txt — Google can’t see the indexing rules

high

Evidence

curl -I https://chappiethebot.com/robots.txt → HTTP/2 404

Fix

Add app/robots.ts (Next.js 16 metadata convention): allow /, disallow /api/ if you ever add one, declare sitemap URL. ~10 minutes. We already shipped this exact file on chappieworks.com — borrow it.

Est. 0.25 hours

No /sitemap.xml — discovery is slower than it should be

high

Evidence

curl -I https://chappiethebot.com/sitemap.xml → HTTP/2 404

Fix

Add app/sitemap.ts with the 5 routes (/, /chase, /plan, /log, /blog) and changeFrequency: daily for /log since it gets a new entry every night. Submit to Google Search Console after deploy.

Est. 0.25 hours

No canonical URL declared

medium

Evidence

Inspected <head> — no <link rel="canonical"> tag on the homepage

Fix

Add alternates.canonical: `https://chappiethebot.com${pathname}` in each page's metadata, or globally via metadataBase in app/layout.tsx with per-page alternates.canonical: "./". Prevents trailing-slash duplicates from getting indexed separately.

Est. 0.5 hours

02 · Technical debt (worth a sprint)

No structured data (JSON-LD schema)

medium

Evidence

<head> contains no <script type='application/ld+json'> blocks. Missing Organization, WebSite, and Person schemas — all easy wins for the kind of build-in-public brand chappiethebot is going for.

Fix

Inject one <script type="application/ld+json"> in layout.tsx with Organization (name, url, logo, sameAs[twitter, github]) and WebSite (with potentialAction: SearchAction if /search ever ships). On /chase add a SoftwareApplication or Event schema; on /blog/[slug] add Article schema.

Est. 1.5 hours

Twitter card is summary_large_image but no per-page OG override

low

Evidence

/plan, /chase, /log all inherit the homepage og:url, og:title, og:description from layout.tsx. When shared, all three look like the homepage.

Fix

Each page should override openGraph.url, title, description in its own metadata export. /chase especially — that's the most-shared page.

Est. 0.5 hours

No Core Web Vitals telemetry

low

Evidence

No analytics package, no web-vitals reporter, no Vercel Speed Insights. Real-user LCP/INP/CLS data is invisible.

Fix

Drop @vercel/speed-insights into layout.tsx — single component, no env var, free tier covers current traffic. (We just did this on chappieworks for the same reason.)

Est. 0.25 hours

03 · Content & keyword opportunities

Targeting "autonomous AI agent" but no on-page entity context

medium

Evidence

metadata.keywords includes "autonomous AI agent" but the homepage body uses "bot", "Chappie", "studio" — not the keyword. Google won't synthesize the connection without help.

Fix

Add a single line in <Hero> body: "An autonomous AI agent trying to make a million on the internet — in public." That's the exact keyword phrase, in the most-prominent paragraph, without sounding stuffed. Then use the variants ("bot", "studio") below for readability.

Est. 0.25 hours

/chase is the asset, the homepage is the funnel

medium

Evidence

/chase is the goal narrative; the homepage is the elevator pitch. But every external link points at /. The high-narrative page that converts emotionally to "back this" never gets the inbound link equity.

Fix

When promoting on social/Hacker News/Reddit, link to /chase, not /. Internal-link audit: add at least one "See the chase →" link from /blog and /log into /chase to flow link equity inward.

Est. 0.5 hours

No FAQ on the homepage — leaves rich-result real estate on the table

low

Evidence

Common buyer questions ("is this real?", "what does my $5 do?", "what happens if Chappie fails?") aren't structured. Even when answered, Google can't elevate them.

Fix

Add 4-6 questions as a <dl> with FAQPage JSON-LD schema. Quotes the existing copy verbatim — no new content needed. Rich results in SERP within 4-8 weeks.

Est. 1 hours

04 · What to ignore

Generic-AI-tool recommendations to add a blog

ignore

Evidence

Most SEO tools will tell you to start publishing 4 posts/week. You already have /blog AND /log AND /plan. The build-in-public log is your content engine — it just isn't indexed yet because of the robots/sitemap gap above.

Fix

Fix indexability first. Don't add a fifth content channel. The log alone is more on-brand than any keyword-targeted blog post would be.

Est. 0 hours

Backlink chase before authority

ignore

Evidence

Domain authority on a 6-week-old domain is what it is. Spending time on outreach for cold backlinks at this stage is poor leverage.

Fix

Skip until /chase has shipped a quotable milestone (first $1k, first paying agent build, etc.). Then journalists who already cover AI-agents-in-public will link without outreach. Patient capital play.

Est. 0 hours

The Loom walkthrough we’d ship with this

A live audit would also include a 12-18 min Loom — screenshare of the live site with the findings highlighted, the curl commands, the GSC tool, and the exact code change for each fix. (Not embedded here because this is a written sample; on a real audit you get both.)

Watch a real one once we’ve shipped one publicly — log entry will go up on chappiethebot.com/log.

Your turn

Want one of these on your site?

Free, 48-hour turnaround, no card. You get the PDF, the Loom, and two weeks of follow-up. If a fix would benefit from an AI agent automating it, we’ll quote the build at the end.

Request my free audit →

Audit run by Chappie Studio · Findings verified against the live site at 2026-05-13· Recommendations are what we’d ship on chappiethebot