Cited Pages AI Citation Audit for GetCited.me

Yes. The plugin displays measurements the hosted service produces; it computes nothing locally. A free account is enough to connect one site. On the free plan, a site whose plugin stays connected and keeps reporting gets 40 answer credits on the 1st of each month. The programme has a monthly budget; once it is spent, sites queue for the next month instead of being refused. Paid plans already reset their credits every period, so the grant does not apply to them.

No, and it is built not to. Yoast, Rank Math, All in One SEO, SEOPress and The SEO Framework keep owning titles, meta and schema. This plugin writes into their fields rather than beside them, and steps aside from anything they already handle.

• Titles and meta descriptions are written to your SEO plugin's own fields - the same rows Yoast SEO, Rank Math or SEOPress write themselves - so nothing is duplicated and nothing is lost if you disable this plugin. All in One SEO keeps these in its own database table rather than in post meta, so on an AIOSEO site the plugin offers the text to copy and does not write it. With no SEO plugin at all there is no field to write to, and the plugin says so instead of inventing one.
• Structured data is skipped entirely when your SEO plugin already outputs it.
• If an SEO plugin already serves llms.txt, this one does not take it over. It links you to that plugin's own setting instead.
• robots.txt is never written as a file. When WordPress generates your robots.txt, the plugin can add the audit's crawler rules as one clearly marked block at the end - after anything Yoast SEO adds, and without editing a line of it. If a real robots.txt file exists, if Rank Math, All in One SEO or SEOPress writes robots.txt from its own editor, or if the file already has rules for the same crawlers, the plugin adds nothing and shows you the lines to paste there instead.

Your site URL and a structural summary of published pages - titles, headings, structured-data types, first paragraphs, word counts, and the SEO title and description your SEO plugin already stores. For posts created from GetCited.me articles, also the post ID, its edit-screen URL, its scheduled date, its permalink and publication date once published, and whether it was trashed or deleted; and, when you search the Articles screen, the words you type. Never post bodies, never drafts or private posts, never visitor data. (Visitors' browsers do request the images inside posts created from GetCited.me articles from the hosts those images live on - that is the browser, not the plugin, and it is described in Third Party Services.) The exact list is in the Third Party Services section above, and nothing is sent until you connect an account. You can also read the exact payload yourself, before it is sent: press Show the data that would be sent on the plugin's Settings screen. It opens /wp-json/cited-pages/v1/inventory for your signed-in administrator session, builds the report and returns it to you without contacting the service. (Typed into the address bar on its own, that address answers 401: WordPress's REST API asks for a one-time value the button supplies.)

No. Suggested page fixes are shown as a preview with a copy button. Of those, only titles and meta descriptions can be applied at all, only when you press Apply on that specific page, and each one saves a backup so a single click undoes it. The site files work the same way: llms.txt, ai.txt and the robots.txt crawler rules are shown as a difference against what your site serves now, published only when you press the button under that difference, and undone with one click - the plugin never publishes them on connect, on opening a screen or on a schedule. An article becomes a WordPress post only when you press Create WordPress draft in the plugin or Create draft in WordPress in the GetCited.me app (that link works once, for ten minutes, and only for the article it was made for), and only as a draft: the plugin never publishes anything, never edits a post you published, and never replaces a draft you edited without asking you first. The scheduled background task never applies or creates anything - it only reports your page inventory, and tells GetCited.me what became of an article-based post (scheduled, published, back to draft, trashed or deleted).

Because a plugin cannot know where they go. An answer-shaped opening replaces the first paragraph of your page; an FAQ block belongs above your related links; a corrected heading outline replaces headings you wrote. Those are positions in your own writing, on your own theme, and GetCited.me marks each suggestion with whether a machine could install it safely rather than guessing. Suggestions that still contain a placeholder are copy-only for the same reason: only you know what belongs there.

No. The plugin loads no JavaScript and no CSS for visitors, and makes no network request from a front-end page view. The llms.txt and ai.txt you publish from it, and the crawler rules it adds to robots.txt, are read from the database only on requests for those three files. On a post created from a GetCited.me article it prints that article's FAQ - and, on a site without an SEO plugin, its Article data - as small JSON-LD blocks, read from the post's own data; and the images that came with the article - except a poster you uploaded to GetCited.me, which is copied to your Media Library - are loaded by visitors' browsers from where they are hosted: api.getcited.me, Unsplash, or the website the image came from (see Third Party Services). Everything else happens in the admin area and in background tasks: the daily summary of your published pages, and a one-off report after an article-based post is scheduled, published, trashed or deleted.

Everything GetCited.me prepared for this site is listed in the plugin - the same list, with the same statuses, as Action Center in the app: briefs, articles being written, finished articles, and what became of each one in WordPress (draft, scheduled, published, or moved to the Trash). A brief links to GetCited.me, where its article is written; a finished article has a full preview. Pressing Create WordPress draft on one article creates one draft post with you as its author: the text as WordPress blocks (nested lists stay nested), the SEO title, meta description and focus keyphrase in your SEO plugin's own fields, the poster image, and the article's FAQ as FAQPage structured data on that post only. On a site without an SEO plugin, the published post also carries its Article structured data (title, address, dates, author, image), printed by this plugin on that post only and never next to an SEO plugin's own. Only a poster you uploaded to GetCited.me is copied into your Media Library; an Unsplash photo or an image from any other site is placed as an image block that loads from where it is hosted (see Third Party Services), and so are the images inside the article text. An Unsplash photo is always shown with its photographer credited and linked, as Unsplash requires, and with Yoast SEO or SEOPress it is also set, by its Unsplash address, as the post's social sharing image. It is a draft: nothing is published until you publish it from the editor. Pressing the button again updates the same draft instead of creating a second one, and never overwrites a draft you edited unless you confirm it (your edited version stays in the post revisions). Create draft in WordPress in the GetCited.me app does the same in one step: it opens this screen on that article with a single-use code, valid for ten minutes, which the plugin checks with GetCited.me before it creates anything - a link opened a second time, opened after the ten minutes, or without its code creates nothing and leaves the button for you to press. Nothing is created by a background task.

Disconnecting from the plugin's settings screen revokes the access token on the service and deletes it from your database. The llms.txt, ai.txt, robots.txt rules and structured data the plugin was publishing are switched off and kept: reconnecting the site to the same GetCited.me website switches them back on exactly as they were, and connecting it to a different website starts clean. If the service cannot be reached at that moment, the token is still deleted from this site, and you can revoke it from your GetCited.me settings - a service your site cannot reach must never be able to hold your site in a connected state. Deleting the plugin from the Plugins screen first asks the service to revoke this site's access token - one request, given up after three seconds; if the service cannot be reached the plugin is deleted anyway and you can revoke the token from your GetCited.me settings - and then removes every option, post meta value and scheduled task it created, and the per-user setting that remembers a dismissed setup notice. Deactivating the plugin revokes nothing and keeps the connection, so reactivating it picks up where it left off. Posts created from GetCited.me articles, and the images added to your Media Library for them, are your content and are kept; only the plugin's own bookkeeping on them is removed, so their FAQ and Article structured data stop being printed.

A connection revoked in GetCited.me (Settings → Disconnect, a new pairing of the same project somewhere else) or one whose credential expired is noticed on the plugin's next request: the plugin forgets the credential, switches off the llms.txt, ai.txt, robots.txt rules and structured data it was serving, stops its daily report, and shows a "connection was revoked - pair again" notice on its screen. Pairing again with a new code restores what the site was publishing.

The plugin's screens are for administrators (manage_options). Listing and reading the articles GetCited.me prepared needs edit_others_posts (Editor and up); creating a WordPress draft from one needs edit_posts. A page fix rewrite spends the plan's monthly page fixes, so it is an administrator's action and also needs permission to edit that page; applying or undoing a title or description needs permission to edit that page.

The admin screen's JavaScript in admin/build/ is compiled. Its full, human-readable source ships with the plugin in admin/src/, together with admin/package.json, admin/package-lock.json, admin/vite.config.ts and admin/tsconfig.json. To rebuild it (Node.js 20 or newer):

1. cd admin
2. npm ci
3. npm run build - type-checks the TypeScript and writes admin/build/ with Vite.