Connect your tools, apply fixes in one click
Connecting your tools to LightSpot turns an audit into fixes actually applied to your site — no copy-paste, no developer ticket. WordPress connects through a bridge plugin installed in one minute; Shopify, Wix and Webflow connect natively in one click. And once Google Search Console is connected, your action plan is reordered by the traffic your pages actually get. For technical teams, a public REST API and an official MCP server drive audits from Claude or your IDE, without leaving your workflow.
Start free trial
From audit to fix, without switching tools
Connecting your CMS to LightSpot links the AI visibility audit directly to the fix: once WordPress, Shopify, or Wix is connected, the safe fixes the audit surfaces — titles and meta descriptions on every CMS, structured data on WordPress — apply to your site with no copy-paste and no developer involved. You stay in your usual tool: LightSpot diagnoses, proposes the fix, then pushes it to the right place through your CMS's official API. Nothing to code, nothing to deploy by hand — a win for an in-house team and for an agency managing several client sites from one account.
WordPress, Shopify, Wix, Webflow: four native integrations
WordPress, Shopify, Wix, and Webflow each have a native integration with LightSpot. WordPress connects through a bridge plugin installed in one minute; Shopify, through its native SEO metafields, Wix, through its blog posts' seoData, and Webflow, through its official API, connect in one click, with no technical setup. Once connected, LightSpot knows exactly where and how to write each fix — the right field, the right format, on the right CMS — without exposing your back office to an unofficial third-party tool. Whichever platform your site runs on, the principle stays the same: connect once, then let fixes land where they belong.
The verified fix: rebuilt, re-audited, proven
Before opening the pull request, our agents don't just trust the fix — they prove it. An isolated sandbox pulls the branch, rebuilds the site, serves it, then re-audits it exactly the way LightSpot audits a live site. The before and after scores are computed on the same grid, and the delta travels with the pull request. So you're not reading a promise of improvement, you're reading a gain measured on the rebuilt site, before anything has been merged. Every verification runs under a cost ceiling, so a stubborn build never turns into open-ended spend.
How it works, from connection to proof
Going from audit to fix follows a simple path. 1. You connect your CMS — a bridge plugin for WordPress (one minute), one click for Shopify, Wix or Webflow. 2. LightSpot audits your site against 46 criteria and flags the safe fixes to apply. 3. Whitelisted fixes apply to your CMS, with a first simulated pass. 4. A real re-audit measures the score gain, and you get a recap by email.
Google Search Console: actions ranked by your real traffic
Connecting Search Console skips OAuth entirely: LightSpot gives you the address of a Google service account, you invite it as a reader on your Search Console property, and we verify the access then match the property to your site. The sync runs daily. We read clicks, impressions, CTR and position, per page and per query, across two rolling 28-day windows — the current period and the previous one — plus a per-country anchor across your international markets. Our agents also flag the queries where an AI Overview is capturing your clicks. None of these numbers ever touch your score. They break ties in your action plan: at equal impact, the action covering your most-visited pages comes first, and the report states that the order is weighted by your real traffic. Available on Eclat and Zenith.
Why fixing fast matters for AI citations
According to the Princeton/ACM SIGKDD 2024 study on AI citation optimization, 76% of Perplexity citations come from content published in the last 30 days, and 65% of AI citations draw on sources under a year old. Fixing issues directly on your CMS, instead of waiting on a ticket or a manual deploy, shortens that lag and keeps your pages inside the freshness window AI engines favor when choosing sources. A native integration turns a convenience into a measurable visibility advantage.
A public API and an MCP server for technical teams
For technical teams, LightSpot exposes a public REST API, documented at /docs/api, and an official MCP server, @lightspot/mcp, installable with one npm command: enough to launch audits and read their results straight from Claude or your IDE, without leaving your environment. The MCP server is read-focused: it triggers audits and surfaces their results, while fixes keep applying through your account's CMS connection. The REST API, in turn, lets you wire LightSpot audits into your own dashboards or internal scripts.
What LightSpot touches, and what it never touches
CMS connections never ask for access to your site's source code: each one goes through the official API — an application password for WordPress, a token for Shopify, a key for Wix, the official API for Webflow — never a direct line into your files. The same guardrails apply everywhere: any page edited by a human since the last audit skipped outright, every applied fix logged and reversible in one click. You keep full traceability of what changed, on which page, and when.
Frequently asked questions
How do I audit my site's AI visibility?
LightSpot audits your site against 46 measurable criteria — 21 SEO and 25 GEO — producing a score out of 100, an A-F grade, and the top 3 priority fixes. Once your CMS is connected, those fixes apply directly to your site, without leaving LightSpot.
Which CMS are natively supported?
WordPress, Shopify, Wix, and Webflow are natively supported. WordPress connects through a bridge plugin installed in one minute; Shopify, through native SEO metafields, Wix, through seoData, and Webflow, through its official API, connect in one click, with no access to your code required.
How do I install the WordPress bridge plugin?
The bridge plugin installs like any WordPress extension, in about a minute: download it from your LightSpot account, activate it on your site, then enter the application password WordPress generates. Meta and content fixes can then apply directly, with nothing to code on your end.
Do I need to hand over Google credentials for Search Console?
No OAuth, no password. LightSpot gives you the address of a Google service account: you invite it as a reader on your Search Console property, we verify the access and match the property to your site. The daily read is limited to clicks, impressions, CTR and position, and it never changes your score.
Do I have to give access to my site's code?
No: WordPress, Shopify, Wix and Webflow all go through their official APIs, never your files or your hosting. No integration touches your code.
Can the MCP server apply fixes from Claude?
No, LightSpot's official MCP server is read-only: it launches audits and reads their results from Claude or your IDE. Applying fixes stays handled by your account's CMS connection, with a simulation pass first and proof of the score gain once it runs.
Other features