Site Audit
Created by Shimecki
Review a site's content, SEO, speed, accessibility, conversion paths, and structured data.
Our developer take
Prioritizing website improvements
Use a production URL to build a small maintenance backlog after launch. Ask for evidence for each issue, then select a few reproducible fixes. Keep measured performance results separate from recommendations inferred from the page.
A practical first workflow
How to use Site Audit
Create an evidence-backed fix list for one public product page.
An AI IDE List walkthrough based on the linked template. These are suggested tasks and review criteria, not results from a hands-on test.
First, add this Bot
Open the official Site Audit template, choose Import Bot, and finish adding it in the Grok Bot app. Open its conversation, then follow the workflow below. If you have not set up the app, follow our installation and connection guide.
What to prepare
- A reachable production URL and one conversion goal.
- A starting scope, such as the landing page and one documentation page.
- Optional performance reports or analytics you want the Bot to consider.
Choose pages and a goal
Provide exact URLs and the intended visitor action. Start with a small scope so each recommendation can point to a concrete example.
Request a cross-discipline audit
Ask for SEO, content, speed, accessibility, conversion, and schema observations. Require evidence URLs and a stated method for measured claims.
Triage the findings
Review the P0/P1/P2 priorities against user impact. Request a specific change and a way to verify each selected fix.
Implement and recheck
Apply one or two fixes, then request a comparison on the same URLs. Save the dated initial report for future monthly comparisons.
First-run example
Replace every [BRACKETED_VALUE] with your details, attach the required files, then send this in the Bot's conversation.
Audit [PUBLIC_PAGE_URL] and [SECOND_PAGE_URL]. The goal is to help [AUDIENCE] complete [CONVERSION_ACTION]. Review SEO, content clarity, speed, accessibility, conversion, and structured data. Return a prioritized P0/P1/P2 table with evidence URL, observed issue, recommended change, and a verification step. For performance claims, include the measurement method and result if actually available; otherwise mark the measurement missing. Start with the five fixes most relevant to the stated goal.
What you should get
Use this checklist to review the first result and request anything missing.
- A prioritized fix list with evidence attached to each finding.
- Specific implementation suggestions and a way to check each fix.
- Measured results separated from observations and unverified hypotheses.
For the next run
Re-audit the same scope after shipping fixes. Use dated reports for a monthly comparison instead of comparing unrelated pages.
If the first run gets stuck
If the URL is unreachable, check that it is public and live. Missing performance-tool access should produce a measurement gap, not an invented score.
What the template includes
Official sourceSummarized from the public listing. The labels below describe capabilities; exact installed skill and connector names are not always published.
Integrations & inputs
- Production website URL
Skills & playbooks
No separate skills documented in the public listing.
Routines
The listing describes a monthly comparison; confirm scheduling during setup.
What to consider
The listing is brief. Confirm which measurements are available and ask for the underlying reports.