Analytics & Reporting
Issues to fix: what each alert means and how to fix it
Every alert Reaudit sends (a Google ranking drop, pages competing for one search, an SEO score drop, new site issues, broken links, an AI visibility gap, a metric or conversion alert) opens an issue with its likely cause, the evidence, and the steps to fix it. Reaudit checks again on its own and closes what is fixed.
An alert tells you something changed. Issues to fix tells you why and what to do. Click any alert in the bell, or open Issues to fix in the sidebar: each issue has three parts, Why it happened, What to do and its status.
Why it happened
Reaudit compares the data before and after the change and names the most likely cause, with the numbers behind it. It says how sure it is: Clear from the data, Likely or Best guess.
- Google ranking drop: another of your pages now ranks instead (two pages competing), many keywords fell on the same day (a Google update or a site-wide problem), the page was edited shortly before, Google added an AI Overview or answer box, new sites now rank above you, or fewer people search it.
- Pages competing for one search: which page to keep (the one with the most clicks, never the homepage when a dedicated page exists) and, for every other page, whether to merge it into the keeper and redirect it, or give it its own focus because it is a different kind of page or earns its own clicks.
- SEO score drop, new site issues, broken links: exactly which issues are new since the previous audit, each with the audit's fix.
- AI visibility gap: which AI engines leave you out for the prompt, which brands they name instead, and which sites their answers cite.
- Metric and conversion alerts: where to look first for that metric (pages and titles for search clicks, channels and tracking for traffic, robots.txt for AI crawlers, the CRO insight for conversions).
What to do
Each step has a button where Reaudit can do the work: Draft it opens Content Studio already filled in (keyword, the page to update, what to change) and links the draft to the issue; Copy the redirect gives you the exact 301 rule for WordPress, Webflow, Shopify, Apache, Netlify or Next.js; Open a fix pull request opens a pull request in your connected GitHub repository (nothing changes until you merge it). Tick a step when it is done.
Status and follow-up
- Open → In progress as soon as a step is ticked or a draft is started.
- Reaudit checks again on its own (a few days after a ranking drop, a week after a cannibalization fix or a published draft, after the next audit or the next AI answers). When the problem is gone the issue closes as Fixed (checked) and, if you acted on it, the fix is marked on your visibility chart so you can see its effect.
- Check again now runs the check immediately. Mark fixed and Dismiss close it yourself; Reopen brings it back.
- The same problem found again updates the open issue instead of sending a new alert, unless it got worse.
- Assign an issue to a teammate from the issue page.
AI agents
Your AI agents (the in-app assistant, the desktop app, MCP clients) see the same issues with list_alert_issues and get_alert_issue. They can draft content and propose fix pull requests through the usual tools, so guardrails and approvals apply, and they tick steps as they go. They cannot close an issue themselves: they run recheck_alert_issue, which closes it only when the data shows it is fixed.