Skip to main content
YAMOYAMOSign in
Official YAMO templatemarketing · 2 plays

URL SEO Audit

Point it at one page and get back a prioritised SEO fix list: what's holding the page back and what to change first, in plain English.

Use this template See a live run
marketing2 playsNo connectors requiredPay per run
What you get

A prioritised audit of one page

A prioritised SEO audit of a single page — what's holding it back and the fixes, in order.

For the owner whose page should be pulling in search traffic and isn't sure why not. Point it at one URL and get back a prioritised fix list: what to change and where, in plain English, highest-impact first. Not a hundred-row checklist.

3 min
to first run
2
plays, run in order
0
connectors required
Per run
pay for what it uses
Anatomy of a playbook

Open it up. See how it works.

A playbook is the way you work, made runnable, built from four ingredients. Tap through each one. The one marked yours is what makes the output specifically about your business.

01 · Goal · fixed

What every run must deliver

Audit one URL for search performance. Research how the page presents in search and what it competes against, then deliver a prioritised list of fixes — the highest-impact changes first, each with a plain-English reason.

// This is the outcome. It doesn't change run to run.
Every run delivers:

A prioritised SEO audit of a single page — what's holding it back and the fixes, in order.

Straight from the template's own definition.

How it runs

Your inputs in, a finished output out

You never touch a prompt. YAMO orchestrates the plays in order; you provide the inputs and read the result.

Input
Your inputs
Play 01
Research the page
Play 02
Write the audit
Output
Prioritised audit
Make it yours

The same template, on your data

Left: the seed run on sample data. Right: the exact same playbook run on your data.

Sample runSeed data
Page to audithttps://basecamp.com (sample)
Referencetarget-keywords.md (example)

→ A real audit, but of a page you do not own. Useful to see the shape.

Your runYour data
Page to auditThe page that should be ranking
ReferenceYour target keywords

→ Your page, judged against your target keywords, with the fixes ranked by what moves your traffic.

Example output · real seed run

See a finished run

An unedited artifact from a seed run on sample inputs. Your runs use your inputs, your references, and your voice.

URL SEO Audit example

Example output — produced by a real run of this template on sample inputs. Sample inputs: url = https://basecamp.com

SEO Audit — https://basecamp.com

Verdict

This page should be winning brand searches ("Basecamp") and core commercial terms ("project management software"), but the research data shows it's absent from visible results for both — the versioned sub-page /5 and third-party help docs are showing up instead. No target-keywords file was provided, so query targets are inferred from the page's topic (project management software), not confirmed by the owner. The single most important fix is to verify why the root domain isn't surfacing — starting with the title tag, meta description, and indexing status — since none of that could be confirmed from search results alone.

Priority fixes

  1. Verify indexing and canonical status of the root domain — check Google Search Console for https://basecamp.com to confirm it's indexed, has no crawl errors, and is set as canonical (not deferring to /5 or a help subdomain). Why: the page didn't appear in provided search results for its own brand name, which is a red flag that needs confirming before any content fix will matter. Effort: quick.

  2. Inspect and rewrite the <title> tag — open the page source of https://basecamp.com and check the actual title text (unverified from search data). Update it to lead with the brand and core value prop, e.g. "Basecamp: Project Management & Team Collaboration Software." Where: HTML <head> / CMS template controlling the root page. Why: search currently surfaces "Basecamp 5 is all new for 2026" instead of the root domain — the title may be too version-specific or missing target terms entirely. Effort: quick.

  3. Write/update the meta description — target 150–160 characters, include the value proposition and a call to action (e.g., "Organize projects, assign tasks, and collaborate with your team. Try Basecamp's new search and live filters."). Where: <meta name="description"> on the root page. Why: no current description was visible in search snippets — this is a free lever to improve click-through once the page ranks. Effort: quick.

  4. Add internal links from high-traffic sub-pages to the root domain — link from /5, help articles, and blog posts back to https://basecamp.com using relevant anchor text. Where: navigation, footer, or in-content links on those sub-pages. Why: the sub-pages and help docs are currently dominating visibility; funneling authority back to the root page may help it compete. Effort: moderate.

  5. Build a clear commercial hero section on the root page — headline and sub-headline that immediately signal "what Basecamp is" and who it's for, distinct from version-specific messaging. Where: main content area (e.g., hero <div>) of the root page. Why: the pages currently ranking (help docs, YouTube walkthroughs) are instructional, not commercial — there's a visible gap for a page that sells the product rather than explains a feature. Effort: moderate.

Competitive gap

  • Depth of instruction wins today: Help articles and YouTube guides ranking in the sample results go deep on specific features (Jump Bar, filters, boolean search operators). The root page likely can't out-instruct these — nor should it try. Closing this gap means linking to them, not replicating them.
  • Format: Competing results favor video walkthroughs and step-by-step guides. Worth noting but not the root page's job to fix — better handled by embedding or linking to existing help content.
  • Missing commercial angle (the gap worth closing): none of the visible ranking content is a sales-oriented "what is Basecamp" landing page. That's the opening — the root domain should own that intent, and currently doesn't appear to.
  • Fragmented brand presence: results point to basecamp-help.com articles and a versioned /5 page rather than a single authoritative root domain — this dilutes brand search equity and is worth consolidating via internal linking and canonical signals.

Backlog

  • Confirm whether basecamp.com appears further down the SERPs (position 10+) for inferred queries — needs a full SERP scan, not visible in current data.
  • Reconcile messaging between /5 (version-specific) and the root domain so search engines and users aren't confused about which is "the" product page.
  • Once target keywords are confirmed by the owner (replace the placeholder target-keywords.md), re-run query-level competitive analysis — current findings are based on inferred topics only.
  • Review whether help subdomain (basecamp-help.com) content should interlink more deliberately with the commercial root page to reduce fragmentation.

This is an unedited artifact from a seed run on sample inputs.

Common questions

Do I need to set up any connectors?

No. This template runs on a fresh account: nothing to connect before your first run.

What do I provide each run?

Each run asks for: page to audit. Swap the target-keywords.md reference for your own doc and the output adapts to your language and priorities.

What does a run cost?

The template is free to copy and no card is required to sign up. When it runs, you pay for exactly what the run used: LLM calls passed through at cost plus the platform operations, itemised on a receipt every run.

Is it mine once I copy it?

Yes. It copies into your account as an editable draft: change the plays, swap the references, set the schedule. Your data and your recipe stay private to your account, and when you publish it as your own service the price is yours to set.

Ready when you are

Make this playbook yours.

Copy it into your account as an editable draft, plug in your data, and run it.

Use this template
Free to copy · pay per run · no card required
FreePay per run
Use this template