Connect your tools, apply fixes in one click
Connecting your CMS 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 and Wix connect natively in one click. The safe fixes an audit surfaces — titles, meta descriptions, structured data — go straight to your CMS. For technical teams, a public REST API and an official MCP server drive audits from Claude or your IDE, without leaving your workflow.
Try for free
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, meta descriptions, structured data — 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: three native integrations
WordPress, Shopify, and Wix each have a native integration with LightSpot. WordPress connects through a bridge plugin installed in one minute; Shopify, through its native SEO metafields, and Wix, through its blog posts' seoData, 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.
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 or Wix. 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 so you see what would happen. 4. A real re-audit measures the score gain, and you get a recap by email.
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.
No access to your code, every fix reversible
LightSpot never asks for access to your site's source code: every connection goes through the CMS's official API — an application password for WordPress, a token for Shopify, a key for Wix — never a direct line into your files. An anti-overwrite guard skips any page a human has edited since the last audit, the first pass always runs as a simulation, and every applied fix stays logged and reversible with 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, and Wix are natively supported. WordPress connects through a bridge plugin installed in one minute; Shopify, through native SEO metafields, and Wix, through seoData, connect in one click, with no access to your code required and no manual configuration to set up.
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 have to give access to my site's code?
No. Connections go through each CMS's official API — WordPress application password, Shopify token, Wix key — never your source code or hosting. LightSpot only reads and writes the SEO fields it's authorized to touch, and every fix stays reversible if you change your mind.
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