Audit a live site, page by page, before any change
Your assistant lists the pages it can find on your site, reads what each one does for search, and proposes one decision per page. Nothing changes until you approve the decision list.
Example
You ask
Our site has been live for three years. Review every page and tell me whether to keep, refresh, merge, redirect, or remove each one.
The assistant
Your assistant finds the site, reads 28 days of Search Console data, and builds an inventory from the saved pages, sitemap, and Search Console. It returns one decision per page with a reason, the competing groups, and a redirect map. It changes nothing until you approve.
Use it when
- You take on a site that is already live for the first time.
- You ask for a full review of an existing site.
- A URL is planned to move, and you need a redirect map for it.
You give it
- The site's domain, saved in RankMySEO. Without RankMySEO, a direct Search Console connection works, and tracked rank is not available.
- Notes on pages you know matter, and any page that exists but is missing from the sitemap, Search Console, and the menu. Your assistant cannot find those pages on its own.
- Your approval of the decision list. No page changes before you give it.
It returns
- A page inventory with one row per URL: title, H1, status code, clicks, impressions, job, and your notes.
- One decision per page (keep, refresh, merge, redirect, or remove), with a one-sentence reason and the number behind it.
- Groups of competing pages, each with the page that should own the keyword.
- A redirect map and a baseline file with the headline numbers and the date they were read.
How the skill runs
Connect the data
Use
list_projectsto find the site andaccount_statusfor the plan. If the site is not saved, ask for the domain and add it withadd_projectafter your yes.Read the headline state
Read
project_overview,search_consolefor 28 days, andsite_issues. Ifsite_issuessays not run yet, no audit has finished; on Starter and abovenext_actionsstarts one, so read it and ask again later.Build the page inventory
Make one row per URL, from
site_pages, the sitemap, Search Console pages, and the homepage navigation. Say what the inventory does not cover, since a page in none of these sources stays unknown until you say it exists.Decide each page
Choose keep, refresh, merge, redirect, or remove. Give each one a reason with its number, such as "Keep: 240 impressions, position 6 for the main query." Confirm with you before any removal.
Find competing pages
Start with
page_updates, then check the biggest keyword each page ranks for insite_pages. Name the page that should own each group, and say which method you used.Plan redirects for moved URLs
Map each old URL to one new URL with a 301 redirect. Avoid chains, and do not send pages to the homepage unless the topic is the homepage. Keep old URLs until Search Console shows no traffic to them for several weeks.
Save the baseline
Save one file with the inventory and decisions, competing groups, redirect map, headline numbers with their date, and open questions. Next steps are seo-keyword-selection, seo-content-refresh, seo-competitors, and seo-maintenance-loop.
Where it stops
- Nothing changes until you approve the decision list. Every page change, removal, and redirect waits for your yes.
- Search Console average position is Google's figure, and the tracked rank is a separate number from RankMySEO. Your assistant quotes the two apart. A high average position with many impressions does not show a win by itself.
- A page with no data gets "not reported" in the table, never an estimated traffic number.
page_updates,site_pages, andnext_actionsneed Starter or above. Without them, your assistant groups pages by the keyword in each title and H1, and says which method it used.
Questions before you install
Can your assistant remove pages from my site?
Only with your confirmation. Your assistant asks first. If it can edit your site's files it makes the change; otherwise it gives you the exact change, so the page returns a real 404 or 410.
What about pages the crawl did not read?
The site_pages answer includes a rankingOffCrawl count, which is the number of ranking keywords on pages the crawl did not read. Your assistant finds those pages through the sitemap and Search Console.
Do I need RankMySEO for this audit?
No. Without RankMySEO, the audit uses a direct Search Console connection, and it says that tracked rank is not available.