Register Website Sources
Website Sources are the URLs the platform reads to check whether your store listing and your website tell the same story. Register your product pages here and each audit compares them against your listing for cross-channel consistency.
You’ll manage them in the project’s Settings → App Context tab, in the Website Sources card.
Before you start
- You need a project with a linked store app.
- Up to 3 sources are scored per audit. You can register more than three; the audit uses the best-quality set, and pinned sources are prioritized.
Add a source manually
1. Enter a URL
In Add a website source, type the URL of a page that represents your product — for example, https://example.com/my-app. Prefer a real product or landing page over a legal, support, or policy page.
2. Validate it
Click Validate. The platform fetches the page and returns a status pill, a quality score, and a short reason:
- ok — usable product content.
- low_content — reachable but thin; scoring may be limited. A page that shows almost no text until JavaScript runs lands here.
- wrong_kind — looks like legal, support, or policy content rather than a product page, or the URL redirects to your homepage.
- unreachable — the platform couldn’t fetch it, for example because your bot protection refused our crawler.
- unchecked — not yet validated.
Validation is a preview — it doesn’t save anything. It lets you see how a URL will be judged before you commit to it.
3. Add it
Click Add. The source is saved with its validated status. You can add a URL even when it validated as unreachable or low_content — the card warns that cross-channel scoring may be limited, but the choice is yours. Duplicate URLs are rejected.
Discover sources automatically
Click Rediscover to have the platform find candidate website sources for you. Discovery runs several strategies — reading your store description, crawling your domain, and web search — and typically takes 30 to 90 seconds.
Discovered candidates respect your robots.txt: a page whose robots.txt disallows our crawler (Apptonomy-Bot) is not read or added. URLs you add yourself are always read.
While it runs, the card shows a Discovery in progress indicator and the Rediscover button is disabled. When it finishes, new sources appear in the table marked with the auto origin and the method that found them (for example, store description, domain crawl, or google search). You can leave the page and come back — discovery keeps running and the card resumes tracking it.
Manage the list
Each row shows the URL, its origin (user for ones you added, auto for discovered ones), status, quality score, and when it was last validated.
- Pin / Pinned — pin a source to prioritize it when the audit picks which sources to score.
- Delete — remove a source. Deleting an auto-discovered source also suppresses it, so a future Rediscover won’t add it back. Deleting a source you added just removes it.
Verify it worked
A saved source appears in the table with its status pill and origin. After the next audit, your registered sources feed the cross-channel consistency check between your listing and your website.
Troubleshooting
A source validated as “wrong_kind”
The URL looks like legal, support, or policy content rather than a product page. Point it at a page that actually markets or describes your app. You can still add it, but it won’t carry much weight in cross-channel scoring.
A source validated as “unreachable” with a 403
Your site’s bot protection refused our crawler, which identifies itself as Apptonomy-Bot. That usually means it blocks unknown bots; check that it lets AI search crawlers such as OAI-SearchBot, PerplexityBot and Googlebot through, since the AI Discovery Engine reports the same block in its recommendations.
Discovery is taking a long time
Discovery normally finishes in 30 to 90 seconds. If it runs longer, the card tells you it’s still working — refresh the page later to see the results. A run that stalls is automatically cleared after a few minutes so you can trigger a fresh one.
A discovered source keeps coming back
Deleting an auto source suppresses it from future discovery, so it shouldn’t reappear. If it does, confirm you deleted it (which suppresses) rather than something else, and that the URL matches — suppression keys off the canonical form of the URL.