# Get a Site Audit > Ask Revnu in chat to audit your website or blog. It fetches your live pages, checks what Google and AI engines actually see, and gives you a prioritised fix list you can hand to a developer or have Revnu ship as a pull request. Canonical: https://revnu.com/docs/site-audit Last updated: 2026-10-18 Ask Revnu "audit my site" and it fetches your real pages, checks what search engines and AI engines actually receive, and tells you what's stopping them from reading you. You get a score, the biggest problem in plain words, and a fix list in **Review**. ### 1. Ask for it in chat Write in chat, for example: - "Audit my site for SEO and AI search." - "Is my blog set up right?" - "Check yourcompany.com/pricing." If you name a page, Revnu audits that page. Otherwise it checks your homepage, a product page and a blog post. ### 2. Read the summary Revnu answers in chat in three lines at most, for example: > 11 of 14 checks pass on yourcompany.com/blog. Biggest one: robots.txt blocks the files your pages load, so Google sees every post blank. Fix list is in your queue. ### 3. Open the fix list in Review The full list is a card in **Review**, ordered by impact. Each item shows what Revnu saw, why it matters and the exact change to make. See [What you'll see](#what-youll-see). ### 4. Get the fixes made Have Revnu open a pull request, hand the card to your developer, or change the setting in your site builder. See [Getting the fixes made](#getting-the-fixes-made). ### 5. Ask for the audit again When the fixes are live, ask for the audit again to check they worked. > **Note:** The audit only reads your site. Revnu doesn't change your website on its own, and marking the fix-list card done in **Review** doesn't change it either. Revnu also runs the audit once by itself when your first post goes live on a blog your site hosts, and when you press **I've Connected It** in the blog setup. ## What it checks Each check is about what your server actually sends, read in that moment: 1. **Pages arrive with real content.** A page that only fills in after JavaScript runs looks empty to crawlers and AI engines. 2. **Correct status codes.** Real pages return 200, and a made-up address returns "not found". 3. **One address per page.** http, https, www and trailing slashes all settle on one form, and the canonical tag agrees with the sitemap. 4. **Structure.** One main heading, a title and description, valid structured data, and FAQs visible on the page as well as in the code. 5. **Discoverable.** robots.txt allows crawling and doesn't block the files your pages need, the sitemap lists real public pages, and llms.txt is present and up to date. 6. **Fresh.** Your newest post is actually live on your site. ### Let AI crawlers in ChatGPT, Perplexity, Claude and the other answer engines each crawl with their own named bots, and Google AI Overviews and AI Mode use Google's index. If robots.txt blocks a search bot such as OAI-SearchBot or PerplexityBot, that engine can't use your pages as a source. Ask Revnu to check: > Check my robots.txt lets ChatGPT, Perplexity, Claude and Google read my site, and tell me what to change if it doesn't. [Try this in Revnu](/sign-up?prompt=Check%20my%20robots.txt%20lets%20ChatGPT%2C%20Perplexity%2C%20Claude%20and%20Google%20read%20my%20site%2C%20and%20tell%20me%20what%20to%20change%20if%20it%20doesn%27t.) [How AI engines choose what to cite](/docs/how-ai-engines-choose-sources) lists the bots and what each one does. ## What you'll see The fix-list card in **Review** is ordered by impact: 1. Problems that make pages invisible or wrong. 2. Problems that split your rankings between two addresses. 3. Missing structure that costs you rich results and AI answers. Each item shows what Revnu saw, why it matters and the exact change to make. It's written so you can forward it to whoever runs your site. Checks that passed sit at the bottom so nobody touches what already works. ## Getting the fixes made There are three ways to get the fixes in. ### Have Revnu open a pull request If your site's code is in a GitHub repo: 1. [Connect the repo](/docs/github-blog-posts) in **Connections**, on the **GitHub** row. 2. Ask in chat, naming the fix: "fix the robots.txt issue from the audit in a pull request." 3. Revnu makes the change on a `revnu/` branch, opens a pull request and sends you the link. It keeps each pull request small and opens a few at a time. 4. You review and merge it on GitHub. Revnu never pushes to main or merges anything. 5. Once it's deployed, say "merged" and ask for the audit again. ### Hand the card to your developer or coding agent The fix list stands on its own, with no Revnu jargon. Copy it from the card and send it to whoever runs your site. ### Make the change in your site builder Sites built in Wix, Webflow, Squarespace, Framer, Lovable or ChatGPT Sites have no repo Revnu can open a pull request on. Many fixes, like a page title, a description or a redirect, are settings in the builder. Ask Revnu where the setting lives in yours, or paste the fix from the card into the builder's own AI assistant and let it make the change. On the [Revnu-hosted blog](/docs/hosted-blog), Revnu can fix post content itself. ## Next step [Connect GitHub for pull requests](/docs/github-blog-posts) ## Frequently asked questions ### How do I get an SEO audit of my website? Ask Revnu in chat: "audit my site for SEO and AI search." It checks your live pages and puts a prioritised fix list in Review. ### Will Revnu change my website during the audit? The audit only reads your pages. Fixes happen when you or your developer make them, or when you ask Revnu for a pull request on your connected repo. ### Can Revnu fix my site without a developer? If your site's repo is on GitHub, connect it and Revnu opens a pull request for you to merge. On a site builder like Wix, Webflow, Lovable or ChatGPT Sites, most fixes are settings you change yourself. Revnu can tell you where they are, or you can paste the fix into the builder's own assistant. ### I approved the audit card. Is Revnu making a pull request? Pull requests start from chat. Ask, for example "make a PR for the fixes from the audit," with your repo connected. Revnu opens small pull requests, a few at a time, and you merge them on GitHub. ### Does the audit check AI search as well as Google? Yes. It checks the things both depend on: real HTML content, structured data, a sitemap, robots.txt and llms.txt. ### How often does Revnu audit my site? Whenever you ask, plus once when your blog connects and once when your first post goes live on your own site.