Conductor Website Monitoring

Conductor Website Monitoring

This connector reads Conductor Website Monitoring (formerly ContentKing), the real-time SEO auditing and change tracking service, through its Reporting API v2 (https://api.cm.conductor.com): monitored websites and segments, health and issue statistics, every tracked page with its SEO data, SEO issues and the pages they affect, broken, redirected and canonicalized links per page, alerts, and log file crawler visits. With a CMS API token it can also queue a page for immediate re-auditing.

Setup (2 minutes)

1. In Conductor Website Monitoring open Account, the Account tab, Integration Tokens (an account admin can see them).
2. Copy the Reporting API token into CONDUCTOR_REPORTING_API_TOKEN. It is read-only and is sent as Authorization: token <token>.
3. Optional: copy the CMS API token into CONDUCTOR_CMS_API_TOKEN to use conductor_monitoring_trigger_page_crawl. Without it that tool answers 401.
4. Run conductor_monitoring_list_websites to check the token.

Workflow

• Start with conductor_monitoring_list_websites: the id is the website_id every other tool needs. conductor_monitoring_list_segments gives segment ids and labels for the scope filter.
• Site health: conductor_monitoring_get_statistics (scope website, segment:<id> or segment_label:<label>; captured_at for a past date) and, as a daily series, conductor_monitoring_get_metrics.
• Issues: conductor_monitoring_list_issues lists issue types with counts; conductor_monitoring_list_affected_pages with an issue name such as title/missing lists the pages.
• Pages: conductor_monitoring_list_pages for all tracked URLs; conductor_monitoring_get_page and conductor_monitoring_get_page_issues for one URL; conductor_monitoring_list_page_broken_links, conductor_monitoring_list_page_redirected_links, conductor_monitoring_list_page_canonicalized_links for its links; conductor_monitoring_inspect_url finds a URL without a website id.
• Alerts: conductor_monitoring_list_alerts, then conductor_monitoring_list_alert_pages for the pages that entered or left an alert.
• Crawlers: conductor_monitoring_get_log_file_analysis for daily visits of search and AI bots (needs Log File Analysis).
• After a fix is published: conductor_monitoring_trigger_page_crawl to re-audit the page now, then conductor_monitoring_get_page_issues a little later.

Reading the answers: URLs must be full and absolute (https://www.example.com/page). Dates are ISO 8601; date ranges take YYYY-MM-DD. Health is a score from 0 to 1000. Issue names have the form <group>/<issue>, e.g. meta_description/duplicate, h1/too_many, links/broken, lighthouse/lcp.

Paging: per_page is 1 to 1000 results. conductor_monitoring_list_pages and the link tools return next_page_cursor: pass it as page_cursor until it is missing (faster than page on sites with more than 10,000 pages). conductor_monitoring_list_affected_pages and conductor_monitoring_list_alert_pages page with page from 1.

Limits and errors: 6 requests per second per IP address; above that the API answers 429 and blocks for a minute, so do not loop over pages faster than needed. 401 means a wrong or missing token, 422 a malformed Authorization header, 400 or 404 an unknown website id or a URL that is not tracked. conductor_monitoring_get_metrics and conductor_monitoring_inspect_url use the Reporting API v1, which Conductor no longer develops and plans to retire.