SEO Audit
A Muse site audit from its own Search Console data, fixes in order, re-measured.
- What
- A Muse site audit from its own Search Console data, fixes in order, re-measured.
- Cost
- Free
- Needs
- Use SEO Audit for Muse to audit <your-site>, from its own Search Console
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
SEO Audit for Muse is a method for auditing a Muse site the way the 2026-10-29 Skill Harbor audit was done: from the site's own data, never from a guess about what Google might do. It starts with Search Console performance data, in bulk, not one page at a time: clicks, impressions and positions by query and by page, over a stated period, with the normal Search Console lag stated honestly (about three days). It then cross-checks with on-site navigation data: which pages visitors actually view, which on-site searches happen, and where the bottleneck really is. A page Google shows but nobody clicks is a title and snippet problem. A page nobody reaches on the site either is not a conversion problem to fix on the page itself. It then works in order, one package at a time, and each package is prepared only, never deployed on its own: hub titles and metas, quick fixes (noindex on login and account pages, homepage heading, install guide), near-miss fiches (titles and metas revised, never rewritten blindly), language-switcher redirects, and crawled but unindexed pages. For unindexed pages, it never rewrites titles first: it checks that the pages are live, gives them internal links, asks for indexing one by one in Search Console, and only then starts a new validation. For bulk title work, it works in proposals first, never live first. Proposals are generated for the whole catalogue, on the home PC when possible so the main machine is not jammed, then reviewed mechanically: every length, pure insertion only, duplicates, and Muse present in every title. Titles that would exceed 60, titles that would collide with an existing Skill title, and approved prototypes are held back, never forced. Only the reviewed lot goes forward, and deployment still waits for a separate go. It states its limits plainly. Estimates are estimates, not promises: a title fix on touched pages is tens of clicks, not hundreds, over one to two months. Generic queries dominated by a large platform are not chased. The Search Console API reads performance data in bulk, but it cannot request indexing for ordinary pages: Google only opens that button in the interface, one URL at a time, and its Indexing API is restricted to job postings and livestreams. Nothing is published, deployed or written to a production database on the strength of this skill alone: every deployment waits for a separate go.
Version:
Quick answer
SEO Audit for Muse audits a Muse site from its own Search Console data, not guesses. It finds near-miss pages with impressions and no clicks, broken links, and crawled but unindexed pages, cross-checks them with on-site navigation, then revises titles and metas in order, and re-measures after deployment before rewriting anything else.
Install
Copy the install package below, then paste it into MuseUse SEO Audit for Muse to audit <your-site>, from its own Search Console data, not guesses. 1. State the property, the period, and the Search Console lag. Use bulk performance data only: clicks, impressions and positions by query and by page. Never copy a number from a summary without recounting it. 2. Find, in order: near-miss pages (positions 4 to 10, impressions, zero clicks), broken links, and crawled but unindexed pages. For each, state the evidence: impressions, position, clicks, and last crawl date when known. 3. Cross-check with on-site navigation for the same period: page views, on-site searches, and install or copy actions. Say plainly whether the bottleneck is on Google (shown, not clicked) or on the site (reached, not converted). Do not fix a page problem when the bottleneck is on Google, and do not rewrite titles when the page is not indexed at all. 4. Prepare fixes as separate packages, prepared only: hub titles and metas (title total 60 characters or less, meta 150 to 160 characters, benefit first, paid warning at the end when a paid API is required), quick fixes, near-miss metas, language redirects, and unindexed pages (live check first, internal links, indexing requests one by one in Search Console, new validation only after a new crawl). 5. For bulk title changes, generate proposals first, on the home PC when possible: insert « Skill » before « for Muse » or « pour Muse », in French also handle the English « for Muse » pattern found in some French titles, check every total at 60 or less, check Muse in every title, hold back titles that would exceed, titles that would duplicate an existing Skill title, and approved prototypes, and review the lot mechanically before anyone applies it. 6. Stop there. Publish nothing, deploy nothing, and touch no production database. Deployment waits for a separate go, and re-measurement waits 7 to 14 days after deployment, impressions AND clicks, not position alone, before anything else is rewritten.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.