外掛標籤
開發者團隊
原文外掛簡介
SummitCite treats Answer Engine Optimization as a closed loop rather than a
one-way broadcast: emit the signals AI engines read, measure which AI crawlers
actually arrive, score the content they lift answers from, and show you where
the two disagree.
Everything runs inside your own WordPress. No API key, no account, no
subscription, and nothing sent to PressRoost servers.
Six things it does
Crawler log. Records requests from known AI crawlers – training,
search and assistant bots – and reports them on one screen: which bots
arrived in the last seven days, how often, when each was last seen, and the
individual requests newest first. Retention is yours to set, from 1 to 3,650
days, pruned daily; 90 by default.
Robots policy. Declares, per bot, whether it may read your site – Allow,
Block, or don’t manage – and writes that into the robots.txt WordPress
already generates, inside one marked block. A separate audit screen fetches
your live /robots.txt and reports, per bot, what you configured against what
the file actually grants, and names the mismatch when there is one.
Schema engine. Emits one Article or BlogPosting block on every eligible
published record, plus a FAQPage and a HowTo block when the content qualifies.
It stands aside entirely when an SEO plugin is already emitting content-level
structured data, and the Schema screen shows that decision per plugin with the
evidence it used. A preview shows the exact JSON-LD it would build for any
record you pick.
llms.txt. Serves a plain-text inventory of your public content at
/llms.txt – a bounded, deterministic document that lists only what you
choose, or a sensible automatic selection until you do. It stands aside when
a file already exists in your site root or when Yoast SEO or Rank Math is set
to provide one.
Answer density. Classifies and scores every post for how well it can
answer a question: coverage, quality and structure, each scored separately and
shown with the raw coverage ratio, the per-dimension points and the algorithm
version that produced them. Scan one post or the whole library, results are
versioned and re-scanned when content changes, and the list is ordered
worst-first so the work that pays is at the top.
Conflict detector. One inventory of what else on the site touches
robots.txt, structured data, llms.txt and answer scoring – five SEO plugin
families, each with the evidence for who owns what, and a recommendation
where ownership is contested. Retest on demand.
One dashboard, one settings screen. The Dashboard rolls the six modules into
a single operational-evidence score with a colour-coded gauge, four summary
cards, a per-component breakdown and 14 days of crawler activity as a bar chart
with the same numbers in an accessible table underneath. Every module’s
controls live on one Settings screen, in one form, saved once.
What the numbers do not mean
Stated here because every figure on the screen is bounded by them:
A recorded visit is a User-Agent claim, not a verified identity. Any
client can send any header, and SummitCite performs no reverse-DNS or IP
reputation check.
The log is a lower bound. SummitCite measures inside WordPress, so a request
answered by a CDN, a reverse proxy or a full-page cache never reaches PHP and
is never counted.
A Block rule asks; it does not enforce. robots.txt is a declaration,
honoured by the crawlers that choose to honour it.
Nothing here guarantees a citation, a ranking or a rich result. Those are
decided by the consumer, not by this plugin.
Three principles
Progressive enhancement. Every emission feature works on WordPress 6.5
with no AI involvement at all. The WordPress 7.0 AI Client API enhances the
AI-driven features where it is present.
No API keys. SummitCite bundles no AI provider. Where AI is used the call
goes through WordPress core, using the connection you configured yourself.
Coexistence first. SummitCite steps aside rather than emitting duplicate
output, and decides on evidence rather than on whether a plugin happens to be
active.
External services
This plugin does not connect to any external service and does not send data
anywhere. There is no account, no API key, no licence check and no usage
telemetry, and nothing about your site leaves your server.
The crawler screens link out to the published bot documentation of the
companies whose crawlers are listed, so you can check which user agent a row
refers to:
OpenAI – https://developers.openai.com/api/docs/bots
Anthropic – https://support.claude.com/en/articles/8896518-does-anthropic-crawl-data-from-the-web-and-how-can-site-owners-block-the-crawler
Perplexity – https://docs.perplexity.ai/guides/bots
Meta – https://developers.facebook.com/docs/sharing/webmasters/web-crawlers/
Common Crawl – https://commoncrawl.org/ccbot
These are plain hyperlinks. They open in a new tab when clicked and are never
requested by the plugin itself, so no request, referrer or site data is sent to
those services. Each site is governed by its own terms of service and privacy
policy.
