| 开发者 | karthikeyanpr |
|---|---|
| 更新时间 | 2026年9月27日 19:47 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
llms.txt that tells AI crawlers what your site is about and which pages to cite.[digispot_breadcrumbs] shortcode for your theme.https://api.digispot.ai, OAuth proxy https://wordpress.digispot.ai):
Powers managed AI generation, rank tracking, and backlink data. Page content, titles, and
prompts are sent only when you run an AI action or a cloud-backed report, and only after
you connect a Digispot account. The OAuth proxy is contacted only during Google sign-in,
so you never have to paste a Google Client ID.
accounts.google.com (sign-in),
www.googleapis.com (Search Console), analyticsdata.googleapis.com and
analyticsadmin.googleapis.com (Analytics 4), mybusiness.googleapis.com,
mybusinessaccountmanagement.googleapis.com,
mybusinessbusinessinformation.googleapis.com and
businessprofileperformance.googleapis.com (Business Profile).
https://api.openai.com - Terms | Privacy
https://api.anthropic.com - Terms | Privacyhttps://generativelanguage.googleapis.com - Terms | Privacyhttps://api.deepseek.com - Terms | Privacyhttps://api.indexnow.org):
If you enable IndexNow, the URLs of posts you publish or update are POSTed to the IndexNow
API so participating search engines can recrawl them. Only URLs and your generated
IndexNow key are sent - never page content.
https://api.digispot.ai):
If — and only if — you switch this on in the plugin settings, Digispot AI reports three
lifecycle events (plugin activated, deactivated, uninstalled) so we can see how many sites
use the plugin and why people stop. When you deactivate, you may optionally pick a reason;
that reason is sent with the event. Nothing is sent while this setting is off, which is
how it ships. What is sent: an opaque random install identifier, the event name, and the
plugin, WordPress and PHP version numbers. What is never sent: your site URL, your email,
usernames, post content, or any other data that identifies you or your site.
https://developers.google.com, https://www.bing.com/toolbox/bingbot.json):
The crawl log module downloads Google's and Bing's published crawler IP-range JSON files
to verify that visiting bots are genuine. These are read-only downloads; no data about
your site is sent.
https://www.googleapis.com/pagespeedonline/v5/runPagespeed):
Used for Core Web Vitals and page-speed reports. Contacted only after you add your own
PageSpeed Insights API key in Settings. The public URL of the page being tested and your
API key are sent - never page content or visitor data.
https://fonts.googleapis.com):
When you generate an Elementor page from a design that uses Google Fonts, that page loads
the chosen font stylesheets from Google Fonts on the front end. Visitors' browsers then
request the fonts from Google, which receives their IP address. Pages that were not
generated with Google Fonts never contact this service.
No. The audit, schema, local SEO, redirects, 404 monitor, sitemaps, crawl log, AI referrals and Search Console and GA4 reports all work without an account. For AI fixes, either paste your own OpenAI, Anthropic, Google Gemini or DeepSeek key, or connect a Digispot account to use managed AI credits instead.
Yes. Go to Settings → Migration, or use the Import step in the setup wizard. It imports meta titles and descriptions, focus keywords, canonical URLs, robots settings, Open Graph and Twitter fields, schema JSON-LD, global settings and redirects. It is safe to run more than once, and it never overwrites data you have already set in Digispot AI.
Yes. Digispot AI detects those plugins and suppresses its own conflicting output, such as canonical URLs and Open Graph tags, so nothing is duplicated. That lets you audit your site and compare before you switch. Once you have imported your data, we recommend keeping one SEO plugin active.
Audits run in small background batches, not on page load. The crawl log and llms.txt are off until you turn them on in Settings → Modules, and you can switch off any module you do not use.
Yes. The SEO panel appears as a sidebar in the block editor, as a meta box under the Classic editor, and inside the Elementor editor. Audits score the rendered page, so Elementor content is analysed correctly.
Yes. Under Settings → AI Provider choose OpenAI, Anthropic, Google Gemini or DeepSeek and paste your key. Content is sent only to the provider you pick, and only when you run an AI action.
Settings → Connections → Google Services, then connect with Google. Sign in and grant access. There is no Client ID or Cloud project to set up. Data is cached in your WordPress database.
llms.txt is a plain-text index at the root of your site that tells AI crawlers what your site is about and which pages matter. Digispot AI generates it from your published content and keeps it up to date. It is optional: turn it on in Settings → Modules.
Googlebot, Bingbot and Google-Extended requests are checked against the IP ranges Google and Microsoft publish. Requests that claim to be one of them from any other IP are marked as spoofed. Other AI crawlers are recorded by user agent and shown as claimed.
No. The 404 monitor separates real missing content from bot scanners and exploit probes. Redirect genuine moved pages with one click, and let probe traffic keep returning 404, which is what Google recommends.
Deleting Digispot AI does not remove your SEO titles, descriptions, focus keywords, schema, redirects or local SEO data by default, so a reinstall picks them up again. Audit caches, Google sync tables and API keys are removed. To wipe everything on uninstall, add add_filter( 'digispot_clear_data_on_uninstall', '__return_true' ); to a must-use plugin or your theme's functions.php before deleting Digispot AI.
No. Page content is sent to an AI provider only when you run an AI action, and only to the provider you configured. See Third-Party Services above for exactly what is sent to whom.