Site Audit is Shimecki's official Marketplace template for auditing a website across search, content, speed, accessibility, conversion, and schema. Its public listing is short, so this review is explicit about what it states and what it leaves out.
Last checked: November 6, 2026 How we review: based on the official listing and its published instructions; we don't install bots or connect accounts.
Open the official Site Audit listing.
What it does
The listing describes a combined audit of SEO, content, speed, accessibility (a11y), conversion rate optimization, and schema markup. Findings are scored, ranked as P0, P1, or P2, and backed by evidence URLs. It also advertises a monthly diff, meaning a comparison against an earlier audit.
The visible instructions are brief. They say the bot works in its own workspace folder, that the site URL stays empty until a human supplies a production URL, and that it must never invent a site or fake Lighthouse, PageSpeed Insights, or other lab metrics. They also tell it not to expand into other bots' jobs.
Who it is for
It suits site owners, marketers, and small teams who want one prioritized list of website issues instead of separate reports for search, speed, and accessibility. The P0/P1/P2 ranking helps decide what to fix first.
It is less suited to teams that need a guaranteed accessibility or legal compliance review, or that expect the bot to make fixes. The listing promises neither.
Integrations and inputs
The only stated input is a production site URL that you provide. The listing does not name integrations, permission scopes, analytics or Search Console connections, or a setup duration. It also does not say how speed data is gathered; the instruction against fake Lighthouse or PSI metrics does not establish that the bot runs those tools itself.
Check the Add preview for any integrations before adding it, and ask your copy where each metric comes from.
Routines
The page lists routines as part of the template but does not publish their names, schedules, or default state. The monthly diff is advertised as a feature, not documented as an enabled routine. Do not assume monthly audits start on their own; confirm in your copy before relying on them.
Safety check
Safety: Site Audit works from a production URL you supply, and its listing does not disclose integrations, permissions, approval rules, or routine settings, so check exactly what access and routines appear in the Add preview and confirm it only reads your site before giving it anything more.
Because the public detail is thin, the safest starting point is a public site URL and nothing else. Do not connect analytics, CMS, or hosting accounts until you have seen what the copy asks for and why. If any routine is on, confirm its schedule and what it reads.
The no-invented-metrics rule is useful, but it does not guarantee that every score is correct. Ask for the evidence URL or source behind each P0 finding before acting on it.
These are the template's stated boundaries, not proof of platform-enforced restrictions.
Step-by-step installation
- Open the official listing and confirm the creator is Shimecki.
- Choose the install action. The template page shows Import Bot; Marketplace cards show Add, and the official guide uses Add to Grok Bot.
- Review the context and integrations in the app preview. Note any access beyond reading a public site.
- Choose Add Bot only after that review. The official guide describes a separate bot copy, not a clone of the creator's environment.
- Reinstall any plugins your copy needs, then give it your production URL.
- Request one audit, check the evidence behind the top findings, and only then decide on routines or extra connections.
Three example tasks
- First audit: "Audit this production URL across SEO, content, speed, accessibility, conversion, and schema. Rank findings P0 to P2 with an evidence URL for each. Mark any metric you could not measure."
- Focus on P0s: "List only the P0 findings from the last audit, explain the evidence, and say what a developer would need to verify."
- Compare over time: "Compare this audit with the previous one and show what improved, what regressed, and what is new."
Limitations and when not to use it
Do not use it as a compliance certification, a code-fixing tool, or a source of lab metrics it has not actually measured. The public listing does not document integrations, scopes, approval rules, or routine schedules, so any workflow that depends on them needs confirmation in your copy.
Alternative templates
- SEO & AEO Desk goes deeper on search: content opportunities, briefs, and AI-question mapping.
- Copy Humanizer fits when audit findings point to weak copy that needs rewriting in your voice.
- Distro Bot covers campaigns and distribution, with higher account access.
FAQ
What does Site Audit check?
The listing names SEO, content, speed, accessibility, conversion, and schema, with scored findings, P0/P1/P2 priorities, and evidence URLs.
Does it run a monthly audit automatically?
A monthly diff is advertised, but the public page does not say a monthly routine is enabled by default or give its schedule. Check your copy.
Will it fix issues on my site?
The listing does not say it edits pages or code. Treat its output as a findings report you act on yourself.
Compare the marketer templates, or return to the Grok Bot templates hub.