By default, ContentKing picks up all on-page elements from the HTML source code of the website.
With this feature enabled, all tracked changes, issue auditing, and alerts in ContentKing will be based on the rendered DOM.
Only for verified websites
If connecting Google Search Console or installing the Cloudflare Worker isn’t possible for you, please contact us for manual website verification.
Effect on web analytics data
If you’re using a non-standard web analytics solution and you want to ensure that ContentKing’s monitoring doesn’t affect your analytics data, make sure to configure custom on-page request blocking in ContentKing.
Custom on-page request blocking
To configure custom on-page request blocking, follow these steps:
How do I know which requests I should block?
If you’re using a non-standard or custom analytics or ads service, you may need to block requests to these services to prevent inflating statistics.
As mentioned above, ContentKing blocks all major analytics and ad services (such as Google Ads, Google Analytics, Adobe Analytics, Hotjar, Mouseflow, etc.) out of the box, so if you are using these, you don’t need to set up custom request blocking.
In case you’re using a custom analytics or ad service, make sure to configure on-page request blocking according to the steps above.
If you are not sure what requests are actually being made by search engines and clients (browsers) when visiting your website, you can easily check this using the browser console:
If you are experiencing inflated statistics and you see any requests related to your analytics or any other tracking solution (such as affiliate tracking), make sure to block requests to these domains as described above.