What happened to ContentKing

Type contentkingapp.com into a browser today and you land on Conductor. The old domain 301-redirects to Conductor's monitoring page, and the old pricing URL drops you straight into a free-trial signup form (both observed on October 18, 2026). The brand is gone. The crawler is not.

Conductor announced the deal on February 16, 2022, describing ContentKing as a "real-time website auditing and monitoring solution" and saying its technology "will be packaged within the Conductor platform". No price was disclosed. Every ContentKing employee moved over, including co-founder and CEO Vincent van Scherpenseel, who had started the Amsterdam company in 2015 with Steven van Vessum. Conductor had raised $150 million from Bregal Sagemount three months earlier.

The product was first sold as Conductor Website Monitoring and has since been renamed Conductor Monitoring. You can still see the seams: the screenshots in Conductor's own help center carry file names like contentking-configuring-alerts-sensitivity, and Conductor's FAQ concedes that "you may see images or other references to these brand names in older content." It is the same codebase under a new sign. And you do not have to buy the wider Conductor suite to use it - per the docs, "if you use Conductor Monitoring on its own, users sign in to Conductor Monitoring directly."

How the always-on crawler works

A desktop crawler like Screaming Frog runs when you tell it to. ContentKing never did, and Conductor Monitoring still does not: "Users don't have to push a button or schedule a crawl." It keeps crawling the site around the clock and, when it finds problems in one area, "learns to check those areas more frequently". The robots.txt file gets special treatment - it is checked every 5 minutes, with an alert if it changes or stops responding.

That matters for one specific kind of disaster. A developer ships a staging robots.txt with Disallow: / on a Friday afternoon. A weekly crawl finds it on Monday, after Google has already started dropping pages. A 5-minute check finds it before anyone has left the office.

Every page change goes into a searchable audit trail, with "up to 60 months of history", so you can answer "when did this title tag change, and who changed it?" months after the fact. The crawler also tracks Core Web Vitals per page, can execute JavaScript, pushes important changes to IndexNow automatically and sends a summary email every Monday morning. Seat counts are unlimited, which is the right call for a tool whose whole point is alerting the developer who broke something.

Alerts, and where they can go

The alerting is the reason to pay for this rather than run a crawler yourself. Conductor's pitch is that "alerts fire the moment something changes and route to the right person at the right sensitivity level", and the settings back it up: each alert type has its own sensitivity, its own trigger list (titles, meta descriptions, H1s, canonicals, main content changes, Lighthouse Web Vitals) and its own recipients.

Alerts arrive by email by default, and can also go to Slack or Microsoft Teams. That is where the delivery options end. Conductor's FAQ says it plainly: "Conductor doesn't offer general-purpose outbound webhooks." If you want an alert to open a Jira ticket or page someone through PagerDuty, you are polling the Conductor API or the Monitoring Reporting API from your own script.

The AI-search pivot

The product page now leads with AI, not SEO: "Protect AI & Search Visibility, 24/7", with issues tagged as SEO or AEO. Most of that is relabelling. One part is genuinely new: log file analysis that picks out AI crawlers by name - OpenAI's GPTBot, OAI-SearchBot and ChatGPT-User, PerplexityBot, Anthropic's ClaudeBot and Claude-User, Meta's crawlers and xAI's GrokBot. If you want to know whether ChatGPT is actually fetching your pricing page, this answers it.

The catch is how the logs get in. Conductor Monitoring "supports only direct integrations" with Cloudflare, Fastly and Akamai. No Splunk, no raw file upload. A site served from its own Nginx box with no CDN in front gets none of this feature.

Two other features sit behind a higher wall. Custom element extraction - tracking a price, a stock flag or a schema field on every page and alerting when it changes - is for "customers on our Enterprise plan". And Conductor's AI features require being on the new subscription plan, so a legacy ContentKing contract does not get them by default.

Pricing: no number on the page

ContentKing used to publish its prices. Its 2021 pricing page carried a range of $99 to $1,999 per month, with "unlimited websites, projects, rechecks and users" and a claim of 2,000+ customers. Conductor's pricing page, checked in October 2026, shows no dollar figure at all. It lists three plans - Essentials ("Try for Free"), Growth ("Request a Demo") and Enterprise ("Contact Sales") - under the line "Pay for what you use".

For monitoring alone, the bill is set by the Page Bundle: "the total number of monitored pages on all of your websites, in total." You set a Page Capacity for each site, with a minimum of 100 pages. Redirects, 404s and server errors "are excluded and you never pay for them", and the price per page falls as the bundle grows. Conductor's own docs cannot agree on the step size - one page says capacity moves "in increments of 1,000 pages", the setup guide says 100 - so ask before you size a contract.

The risk-free part is real. The trial runs 21 days with no credit card, and paid plans come with a 30-day money-back guarantee "within 30 days of your first payment". You pay by credit card and can cancel at any time.

Start the 21-day Conductor Monitoring trial

Limits the product page leaves out

The crawler stops reading a URL at 1MB, or 2MB with JavaScript rendering on, and gives each page 10 seconds to render. A long category page with hundreds of inline product cards, or a slow single-page app, can hit either cap - and what lies past it is invisible to the monitor.

User reviews on G2 and Capterra rate the product highly, but the same complaints keep coming up in them. It is expensive for small sites. Per-page billing makes the cost hard to estimate before you have crawled the site. Non-technical users find the issue lists overwhelming. The Excel export is clunky. And monitoring itself does no rank tracking, so you still need a separate tool - or Conductor's wider suite - to see what a broken template cost you in positions.

Cheaper ways to get most of it

For a small site, Little Warden is the obvious comparison. Checked in October 2026, it costs £24.99/month for 20 URLs, £34.99 for 100 URLs, £59.99 for 650 URLs and £149.99 for 5,000 URLs, with data kept for two weeks to six months depending on plan. It is built to watch a short list of important URLs rather than the whole site. What you lose is the full-site crawl and the 60-month history.

A scheduled crawl is the other route. Screaming Frog and Sitebulb can both run on a timetable and compare one crawl with the last, which catches most regressions within a day or a week. That is fine for a blog that changes weekly, and not fine for a store that deploys ten times a day. At the far end, BrightEdge competes with Conductor's whole suite rather than with monitoring alone.

Verdict

Conductor Monitoring is still the ContentKing that SEO teams liked: a crawler that never stops, alerts that reach the right person, and a change history long enough to settle arguments. Buy it if you run a large site that deploys often, where a bad robots.txt or a lost canonical costs real revenue per hour, and if your traffic already passes through Cloudflare, Fastly or Akamai so the AI-crawler logs work.

Skip it if your site has a few hundred pages and changes weekly. Little Warden covers the outage cases from £24.99/month, and a scheduled Sitebulb or Screaming Frog crawl covers the rest. Skip it too if you need alerts piped into your own systems by webhook, because there are none. Either way, use the 21-day trial to get a real Page Bundle quote before anyone signs - without a public price, that quote is the only number you will get.

Try Conductor Monitoring free for 21 days