SEO Content Publisher for 8ight.ai

變更記錄

1.9.4

• Fix: when the optional layout dresses the site’s own posts, it now dresses only the post itself. On themes that print the post body directly and run other content (for example an inserted footer page) through the content filter, that other content could take the post’s styling. Nothing changes on sites where the option is off.
• New: the platform can set a published article’s categories without republishing it. Only the categories change; the title, text and dates stay exactly as they are. Posts the site owner wrote are never touched.

1.9.3

• New: the optional article layout can also dress the site’s own posts (ones not published through this plugin), when the platform turns that on for the site. The theme’s own title stays the page heading, the stored posts are never edited, and every word stays on the page in the same order. Nothing changes on sites where it is off.

1.9.2

• New: an optional style for the “Related reading” box at the end of each article, in the site’s own colours and heading font, off by default and switched on per site from the platform. It is applied when the page is shown; the stored posts are never edited and every word and link stays as it was. Text colours are kept readable (WCAG AA) on the site’s background, links show a visible keyboard focus, and themes that print the post body without running the_content are covered too. Nothing changes on sites where it is off.
• Fix: related reading links whose title was cut short when the article was written now show the linked post’s full title. Only links to a post on the same site whose title starts with the stored text are changed; nothing stored is edited.
• New: an optional small site-wide stylesheet set from the platform (for example to hide a broken third-party widget on every page). Empty by default; nothing is printed then.

1.9.1

• Fix: the optional article skin now also applies on themes that print the post body without running the_content. Nothing changes on sites where the skin is off.

1.9.0

• New: an optional Google “Add to preferred sources” button after each post (or in the footer), off by default and switched on per site from the platform once the site is confirmed in Google’s source preferences tool. It is added when the page is shown; the stored posts are never edited. The button follows the site’s language and a light or dark theme. A preview mode shows it only to signed-in editors.

1.8.0

• New: an optional article layout (“article skin”), off by default and switched on per site from the platform. It changes only how an article is shown; the stored post is never edited, and every word of it stays on the page. Two layouts ship: fl-beauty and nh-editorial. A preview mode shows the layout only to signed-in editors, and a site run for an agency client cannot be switched on without the client’s approval date.
• Fixed: republishing an article without categories no longer resets its categories to the default.
• Fixed: llms.txt no longer says articles are “reviewed by domain experts”; it says they are written with AI assistance.

1.7.2

• Fixed: on sites with a dark brand colour, the audio player’s controls keep a light background so the play button stays visible.

1.7.1

• Fixed: the “Listen to article” player stays in the article’s reading column instead of stretching across the full page on some themes.

1.7.0

• Changed: the “Listen to article” player no longer shows a headphones emoji. Some themes drew it as a very large picture over the label. Where the site has an audio host picture set, the player shows that picture in the site’s colours instead. Nothing stored in your posts is changed: the swap happens when the page is shown, and the audio itself is untouched.
• Added: an optional audio host setting, sent with a publish or through the settings endpoint, and reported by /health.
• Includes 1.6.1: robots.txt no longer lists /llms.txt as a “Sitemap:”.

1.6.1

• Fixed: robots.txt no longer lists /llms.txt as a “Sitemap:” (it is not a sitemap, and search engines tried to read it as one). It is mentioned as a comment instead; /llms.txt itself is unchanged.

1.6.0

• Added: an SEO title. Each article can carry a short title for search results (the page’s
• Changed: on sites without an SEO plugin, the business is described as a LocalBusiness in structured data only when a street address is set (Google requires one); otherwise it stays an Organization with its phone and service area.
• The /health endpoint lists the features this version supports.
• Per-article structured data blocks are marked data-origin=”article”, so a site audit can tell them from the theme’s or SEO plugin’s own.
• The comment above the AI crawler lines in robots.txt no longer carries a product name.

1.5.0

• Redesigned the settings page: a clear strip of what the platform has done on your site (articles published, last article, last IndexNow push, auto publish), then numbered sections for the connection, publishing options, the business details the platform prints on your pages, recent activity and how to connect. Current 8ight.AI logo throughout; the old artwork is gone.
• The dashboard at app.8ight.ai is an allowed origin for the REST API.

1.4.0

• Added: IndexNow. Every article or page that goes live or changes is announced to Bing, Yandex, Seznam and Naver the moment it publishes (and to the AI assistants that read Bing’s index), instead of waiting for the next crawl. A small key file on your site proves ownership; nothing else changes. Google is not part of IndexNow and keeps finding pages through your sitemap.

1.3.5

• Added: a lead form you can place on any page with [8ight_lead_form] – name, phone and an optional message, with the campaign details of the click recorded alongside the enquiry, and a redirect to your own thank-you page once it has actually sent.
• Added: a page can be published as noindex, so a thank-you or confirmation page stays out of search results and out of your sitemap.

1.3.4

• Fixed: on sites with a page cache (LiteSpeed, WP Rocket, W3 Total Cache and others), a newly published or updated article could keep showing the old version to visitors. The page cache is now cleared automatically after every publish.

1.3.3

• Fixed: on some themes the Blog page opened empty even though articles were published, because the theme’s archive template replaced the page’s own content. The blog index setting can now be corrected from your 8ight.AI dashboard, and the site tagline can be kept accurate too.

1.3.2

• Fixed: when an article’s main image was replaced after publishing, the old image stayed as the social-share preview on Facebook and LinkedIn. The share image now always matches the image on the page.

1.3.1

• Fixed: publishing an article with a category the site did not have yet failed with a fatal error (a WordPress admin-only function was called on a REST request). New categories are now created with core wp_insert_term().

1.3.0

• Site-wide traffic insights: pageviews are now reported for every page on your site (homepage and service pages included), not only blog posts. As before, only the page URL and referrer are sent – no cookies and no personal data.

1.2.0

• Sitemap cache is flushed automatically after every publish (Rank Math and Yoast), so new articles appear in the sitemap immediately.
• New /health endpoint for remote diagnostics: plugin version, indexability, published counts, active SEO plugin.
• New /fix-settings endpoint: repair search-engine visibility (blog_public) and flush the sitemap cache on demand.
• The plugin now keeps itself up to date via WordPress auto-updates.

1.1.0

• Traffic insights: the plugin now reports each article pageview and its referrer to the 8ight.ai platform, so you can see real organic-click counts for your published content directly in your 8ight.ai dashboard — no Google Search Console connection required. Only the page URL and referrer are sent; no cookies and no personal data are collected.

1.0.9

• Per-post extra JSON-LD schemas via the schemas field on the /publish endpoint. Sites with Yoast, Rank Math, SEOPress or AIOSEO already emit Article + Organization + WebPage — but none of them auto-generate the Service, FAQPage-per-post, HowTo, Product or Review schemas that AI answer engines (ChatGPT, Claude, Perplexity, Gemini) look for when picking a citation. This release lets 8ight.ai push those extra schemas per article; the plugin stores them in post_meta and emits them from a wp_head hook at render-time, ADDING to (not replacing) whatever the site’s SEO plugin already provides.

1.0.8

• Native schema injection for sites WITHOUT an SEO plugin (e.g. Yoast/Rank Math/SEOPress/AIOSEO). The plugin now emits a clean Article + BreadcrumbList + WebPage + Organization/LocalBusiness + WebSite @graph in so ChatGPT / Claude / Perplexity / Gemini / Google AI Mode can extract rich citations from these sites.
• Auto-detects competing SEO plugins and skips injection when present — no duplicate or conflicting schema.
• New /wp-json/8ight-ai/v1/business-info endpoint lets the 8ight.ai dashboard push phone / address / service-area / logo to the plugin, which then promotes Organization → LocalBusiness automatically.

1.0.7

• Rank Math compat: fix the BreadcrumbList position field being emitted as a JSON string (“1”) instead of an integer (1) — Google Rich Results flagged this as invalid. Hooks into rank_math/json_ld and coerces the field to int. No-op when Rank Math isn’t active.

1.0.6

• AI discoverability: robots.txt now appends explicit Allow: / directives for GPTBot, ClaudeBot, PerplexityBot, CCBot, Google-Extended, Applebot-Extended, Bytespider, Meta-ExternalAgent, Amazonbot, cohere-ai, YouBot, Diffbot and others — so AI search engines know they may crawl + cite the site.
• New /llms.txt endpoint at the site root: a markdown index of every published post (with one-line summary) in the format adopted by ChatGPT / Claude / Perplexity crawlers. Built dynamically from wp_posts at request time — no maintenance, always current.
• Both files are linked from each other (robots.txt advertises llms.txt as a Sitemap reference).

1.0.5

• New head_css param on /publish — raw CSS stored in post meta and emitted in via wp_head. Lets the publisher patch theme-specific layout issues per-post without editing the theme or relying on Customizer Additional CSS.

1.0.4

• Preserve original post_modified on UPDATE so themes no longer show “Last updated: today” after every content backfill.
• New set_modified_at param on /publish to force a specific modified date.
• New /set-modified-date endpoint for date-only retroactive fixes.
• Accept post_type param (‘post’ default, ‘page’ for evergreen landing pages).
• Refreshed admin settings header: round 8ight.ai logo at the top, removed legacy banner image.

1.0.2

• Escaped all output per WordPress coding standards
• Replaced date() with gmdate()
• Replaced parse_url() with wp_parse_url()
• Replaced unlink() with wp_delete_file()
• Added sanitize_callback to all register_setting calls
• Enqueued CSS and JS properly
• Fixed stable tag mismatch

1.0.0

• Initial release