π Understand AI visibility fact checks
AI visibility checks compare information found across your website and other public sources. A flagged item does not always mean your site is incorrect. It may indicate that information is missing, inconsistent, outdated, or difficult for search systems to confirm.
Review the flagged source and compare it with your preferred business information. Check your business name, address, phone number, website, privacy policy, author details, and other important facts for consistent spelling and formatting.
π§ Resolve an email mismatch
An email mismatch means the email stated in an AI answer, or on your website, does not exactly match the email in your Brand Vault. If you have no Brand Vault, it is compared against the email found on your website. Emails are compared after ignoring letter case and any "mailto:" prefix. Common causes are an outdated or different address in the Brand Vault, a different domain in the email, or an AI model quoting an old address. A contact email that only appears after JavaScript loads, or is built from an image, can also be missed on the website. **
- Identify the email address shown in the fact-check result.
- Confirm which email address your business currently uses.
- Update outdated email addresses on your website, contact pages, privacy policy, terms, social profiles, and business listings.
- Use the same format and domain wherever possible.
- Make sure the correct page is publicly accessible and does not require a login.
- Run the check again after search systems have had time to recrawl the updated content.
If different email addresses are intentional, clearly explain their purpose, such as separate addresses for privacy requests and general support.
π Fix a βtoo many redirectsβ privacy policy error
This error occurs when the privacy policy URL sends visitors through repeated or circular redirects instead of loading the page. Common causes include conflicting HTTP-to-HTTPS rules, www and non-www rules, incorrect canonical settings, or redirect rules added by a CDN, hosting provider, plugin, or server configuration.
- Open the privacy policy URL in a private browser window and confirm whether it loads.
- Use the final HTTPS URL in your website navigation, sitemap, and structured data.
- Check that the URL does not redirect between HTTP and HTTPS repeatedly.
- Check that www and non-www versions resolve to one preferred version only.
- Review redirect rules in your hosting control panel, server configuration, CDN, and SEO or security plugins.
- Remove duplicate or circular rules, then save the changes.
- Clear website, CDN, and browser caches.
- Test the URL again and confirm it returns a successful page response rather than another redirect.
Do not redirect the privacy policy to the homepage or another unrelated page. The final URL should load the complete privacy policy content directly.
β Verify the fix
After making changes, confirm that the privacy policy opens in a private browser window, uses one stable HTTPS URL, and is linked from your website. Check that the email and other business facts match across your public pages. Re-run the AI visibility check after the updated pages are crawled.
If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.