SEO page audit
Audit named pages for how well search engines and AI answers can find and understand them: titles, headings, meta, links, structured data and speed. Ranked fixes.
In Lobstack: Skills › Library › Add
What your agent will do.
Someone wants to know why pages are not showing up in search or AI answers, or what to fix first on a site or a new page.
- 01
Confirm the pages and the searches each one should win. A page with no target search cannot be judged.
- 02
Read each page as it renders and note the title, the meta description, the main heading, the heading order, and whether the opening paragraph answers the search plainly.
- 03
Check the basics: the page can be indexed (no noindex, allowed by robots.txt, in the sitemap), has one canonical address, loads without errors, and its images have alt text.
- 04
Check links: which pages link to it, broken links going out, and whether link text says where it leads.
- 05
Check structured data where it fits — product, article, FAQ — and that it matches what the page shows.
- 06
Run the target searches yourself. Note who ranks, and what their pages do that this one does not.
- 07
Post a document with fixes in a table ranked by impact and effort, with the exact new wording where the fix is copy. Do not edit the site; ask before any change.
Never promise rankings or traffic. Say what is likely to help, and why.
The whole SKILL.md: 35 lines of Markdown.
Add it in the app from Skills › Library, or copy it and paste it into Skills › Add a skill.
---name: seo-page-auditdescription: "Audit named pages for how well search engines and AI answers can find and understand them: titles, headings, meta, links, structured data and speed. Ranked fixes."metadata: title: "SEO page audit" category: marketing tags: [seo, website]--- ## When to use this Someone wants to know why pages are not showing up in search or AI answers, orwhat to fix first on a site or a new page. ## How 1. Confirm the pages and the searches each one should win. A page with no target search cannot be judged.2. Read each page as it renders and note the title, the meta description, the main heading, the heading order, and whether the opening paragraph answers the search plainly.3. Check the basics: the page can be indexed (no noindex, allowed by robots.txt, in the sitemap), has one canonical address, loads without errors, and its images have alt text.4. Check links: which pages link to it, broken links going out, and whether link text says where it leads.5. Check structured data where it fits -- product, article, FAQ -- and that it matches what the page shows.6. Run the target searches yourself. Note who ranks, and what their pages do that this one does not.7. Post a document with fixes in a table ranked by impact and effort, with the exact new wording where the fix is copy. Do not edit the site; ask before any change. Never promise rankings or traffic. Say what is likely to help, and why.
- Marketing
SEO
Audits pages for search and AI answers, and compares them with named competitors.
4 tools · 2 skills · Runs on a schedule - Marketing
Growth Analyst
A weekly read of traffic, signups and search, per channel and per page, with what to repeat and what to fix.
5 tools · 2 skills · Runs on a schedule
- Marketing
Email sequence
Draft a 3 to 5 email sequence (onboarding, nurture or win-back) with one goal, the timing, and a single ask per email. Drafts only; never sends.
SKILL.md · App - Marketing
Tracked links per channel
Give every channel in a launch its own tracked link — source, medium, campaign — so the results can be read per channel instead of guessed.
SKILL.md · App - Marketing
Receipt for every post
After each approved post goes out, write one row to the Distribution table: channel, live link, tracked link, who approved it and when, so what was published is a record, not a claim.
SKILL.md · App - Engineering
Commit message from a diff
Write a commit message from a diff: a subject line that states what was found, then prose explaining why the change was made.
SKILL.md · App - Engineering
Triage a failing build
Triage a red CI run: find the first real failure, attribute it to a change, and say whether the code is wrong or the runner was.
SKILL.md · App - Engineering
Review what a linter cannot
Review a change for what a linter cannot see: whether it is correct, what it breaks elsewhere, and which parallel list it forgot to update.
SKILL.md · App