Livada SEO Lite
| 开发者 | florinlivada |
|---|---|
| 更新时间 | 2026年10月20日 01:54 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1.2 |
| 版权: | GPL-2.0-or-later |
| 版权网址: | 版权信息 |
详情介绍:
Livada SEO Lite is a free SEO plugin for small local businesses, with business schema for campgrounds, hotels, B&Bs and restaurants. It has no licence key, no trial period and no locked feature. It adds no JavaScript file to your pages; its only front-end file is a stylesheet of under 1 KB, loaded only on pages that show breadcrumbs.
What's in the box
- Meta — title templates, meta description, canonical URL and robots directives
- XML sitemap — posts, pages and the post types you choose
- Schema (JSON-LD) — WebSite, Article, and a business entity (Campground, Hotel, Bed & Breakfast, Restaurant, Store and other local-business types), filled in once from your business details
- Open Graph & Twitter Cards — filled in automatically, with a per-post image override
- Breadcrumbs — the
[livada_breadcrumbs]shortcode and thelivada_seo_breadcrumbs()template tag - On-page analysis — 20 checks, including a Flesch reading-ease score, recalculated each time you save a post and listed in the SEO box
- Robots.txt — an editable virtual robots.txt with a sitemap line
- Redirects & 404 Monitor — 301 and 302 redirects (regex patterns supported), CSV import and export, and a 404 log from which you can create a redirect in one click
- AI suggestions (optional) — title, meta description and focus keyword suggestions from Anthropic Claude, OpenAI or Google Gemini, using your own API key
- Image alt-text — lists the images that have no alt text and lets you fill it in from one screen; optional AI suggestions (Anthropic only)
- Importers — Yoast SEO, Rank Math, All in One SEO and SEOPress (see "Migrating from another SEO plugin" below)
- Migration Verify — under Livada SEO → Migration Verify, tick the pages to check (or type an address of your site), take a "before" snapshot of what they publish in their
<head>, run your import, then compare: each tag is shown as Unchanged, Changed, Missing or Added. Also available through the REST API and WordPress Abilities - AEO (AI assistants) —
/llms.txtand/llms-full.txt(a plain-text summary of your business with links to your main pages), your business description, founding date, founder and areas of expertise added to your business schema, snippet directives (max-snippet:-1) and optional content markers. Settings under Livada SEO → General, section AEO - REST API — settings, per-post SEO data, on-page analysis, redirects and 404s, imports, image alt-text, sitemap tools and more, under
/wp-json/livada-seo/v1/(administrator accounts only) - AI agent discovery — the plugin registers its actions with WordPress's Abilities API (WordPress 6.9 and later), so an MCP adapter plugin can offer them to AI tools, and it publishes an API catalog and an MCP server card that describe its REST API (see "What this plugin publishes on your site" below). It does not run an MCP server itself
- Checkable migrations — Migration Verify lets you compare a page's head tags before and after you switch from another SEO plugin, from its own admin screen, instead of assuming nothing was lost
- Ready for AI assistants — llms.txt, business details for AI and snippet directives are included, produced by your own site with no external service
- Light on the front end — no JavaScript file, and a stylesheet of under 1 KB only on pages that show breadcrumbs
- Your business described once — enter your name, address, phone and opening hours once, and every page publishes them as structured data
- AI is optional and yours — bring your own API key; the plugin does not meter, resell or proxy anything
- Camping, hotel, B&B and restaurant sites
- Single-location local businesses
- Developers who want code they can read and modify
- It does not promise rankings, and it cannot make an AI assistant read or cite your site.
/llms.txtis a plain-text summary your site publishes; no assistant is obliged to use it. - One business location per site. Several locations are in Livada SEO Pro, a separate plugin.
- It does not run an MCP server. It registers its actions with WordPress's Abilities API (WordPress 6.9 and later) so an MCP adapter plugin can offer them.
- The AI Visibility Score module in the code is not reachable from the admin in this version; nothing is sent to Livada unless custom code runs it.
/sitemap.xmland a virtual/robots.txt/llms.txtand/llms-full.txt: a plain-text (Markdown) summary for AI assistants, built from your Schema settings and the AEO fields: business name, type, city, contact details, areas of expertise (or your post categories), links to up to 12 pages (50 in the full version) and, in the full version, your latest 100 posts. Password-protected pages and pages set to noindex are left out. Both files are sent withX-Robots-Tag: noindex. On by default; untick Publish /llms.txt and /llms-full.txt under Livada SEO → General (section AEO) to stop publishing them.- With AEO on (the default):
max-snippet:-1,max-image-preview:largeandmax-video-preview:-1added to the robots meta tag, and anX-Robots-Tag: max-snippet:-1, max-image-preview:largeresponse header, never on a page set to noindex (untick Snippet length); on posts and pages, meta tags namedsummary,topic,subject,classification,target,audience,coverage,distribution,ratingandrevisit-after; and adata-ai-summaryattribute on the first paragraph plus a schema.orgAnswerwrapper after headings ending with "?" (untick Content markers). Untick Turn on AEO to stop all of these at once. /.well-known/api-catalog, plus aLink: rel="api-catalog"header on your pages; an MCP server card at/.well-known/mcp/server-card.json(also answered at/.well-known/mcp/server-cards.jsonand/.well-known/mcp.json); and/auth.md, which says that the REST API uses WordPress Application Passwords. They only describe the REST API, which accepts administrator accounts only. They are on by default and this version has no switch for them in the admin: a developer can turn them off by settingagent_readiness_enabledtofalsein thelivada_seo_lite_settingsoption, then saving Settings → Permalinks once so the old addresses stop answering.- A Markdown version of a post or page, only for requests that send
Accept: text/markdown. It is on by default; setmarkdown_negotiation_enabledtofalsein the same option to turn it off. - Off by default, and with no admin switch in this version: a text-and-data-mining rights signal (W3C TDMRep) made of
/.well-known/tdmrep.json,tdm-reservationheaders and meta tags. It is published only if a developer setstdm_reservationtoreservedornot_reservedin the same option.
- 404 Monitor — for each missing URL it stores the requested path, a hit counter, the date of the last hit, the referring page and the visitor's browser user-agent (first 255 characters). It does not store IP addresses. Nothing expires by itself: delete rows one by one, or purge the whole log, under Livada SEO → 404 Monitor.
- Activity Log — records, with the WordPress user and the time, each save of the settings (only how many settings changed, never their values), each change to the business locations (only how many there were and are), each AI suggestion of a title, a description or a focus keyword (only its type and length, never its text), each redirect added (with its two addresses) or deleted, and each time the log is cleared. It keeps the latest 1,000 entries.
- Redirects — each redirect stores how many times it was used and the date of its last use, and nothing about the visitor. Each use schedules one short WordPress background task (WP-Cron) that updates those two values.
- API keys — see "Where is my API key stored?" in the FAQ.
安装:
- Upload the
livada-seo-litefolder to/wp-content/plugins/, or install directly from the WordPress.org Plugins screen. - Activate the plugin through the Plugins menu in WordPress.
- Go to Livada SEO → Schema to describe your business (name, address, phone, hours).
- Go to Livada SEO → General to (optionally) add an AI provider API key for suggestions. Image alt-text suggestions need an Anthropic key.
- (Optional) Migrate from another SEO plugin under Livada SEO → Tools.
- Keep the other plugin active during the import. Under Livada SEO → Migration Verify, tick your home page and your main pages and click Take the before snapshot.
- Go to Livada SEO → Tools and click the matching Import from … button.
- The import runs in batches. For each post it copies what the other plugin stored: SEO title, meta description, focus keyword, canonical URL, social image and noindex/nofollow settings. It then copies the other plugin's 301 and 302 redirects, as exact-match redirects, when it has any. The Yoast SEO and Rank Math imports also copy the site-wide title templates (home page, posts, pages, categories and tags), the home page description and your social profile URLs; the SEOPress and All in One SEO imports do not copy site-wide settings, so check Titles & Metas and Social afterwards. A template variable this plugin does not have (for example a current-year variable) is not converted: in a post's own title or description it appears as typed, and a site-wide template that uses one is not copied. The import result names them.
- Per-post fields: empty values are skipped, but a value the other plugin still holds replaces the one saved here, so run the import before you edit posts in this plugin, and be aware that running it again overwrites later edits. Site-wide settings you have already changed in this plugin are kept.
- Review your redirects under Livada SEO → Redirects. Redirects of another type (307, 410, 451) and Rank Math redirects that are not exact matches are skipped and counted in the result line. The SEOPress and All in One SEO imports copy each redirect's source and target as plain text and do not read the other plugin's regular-expression option.
- After the import succeeds, deactivate the other plugin, go back to Livada SEO → Migration Verify, tick the same pages and click Compare with the snapshot. A tag shown as Missing was published before and is gone now: fix it before you delete the other plugin.
屏幕截图:
常见问题:
Will it improve my Google ranking?
No plugin can promise that. It publishes your titles, descriptions, sitemap and business structured data correctly, and Migration Verify checks that a migration did not drop any of them. Your content still decides your ranking.
Is it really free? What is the catch?
No licence key, no trial, nothing disabled or time-limited. Livada SEO Pro is a separate plugin with extra features (several locations, hreflang, WooCommerce schemas, Site Audit, bulk tools); the Dashboard shows one box that describes it, and nothing else in this plugin asks you to buy it.
Does it work if my site is set to "Discourage search engines"?
Yes. Since 1.1.7, while that box is ticked under Settings → Reading, the plugin publishes no sitemap and no /llms.txt, and keeps WordPress's own robots.txt.
Does it slow my site down?
It adds no JavaScript file to your pages and one stylesheet of under 1 KB, only on pages that show breadcrumbs. We have not published speed benchmarks.
Does it send data to Livada?
In normal use it sends nothing to Livada. The only requests it sends to another party are the optional AI requests, with your own API key, described under "External services".
Why does it publish /llms.txt?
It is on by default and costs nothing; untick Publish /llms.txt and /llms-full.txt under Livada SEO → General to stop. Password-protected and noindex pages are left out.
Does it work with Elementor?
Yes. The on-page analysis reads the content Elementor renders, so pages built with Elementor are scored on their real text.
Does it import from Yoast, Rank Math or another SEO plugin without losing data?
Yes — Livada SEO → Tools imports titles, meta descriptions, focus keywords, canonical URLs, robots directives and redirects from Yoast SEO, Rank Math, All in One SEO and SEOPress. Run Migration Verify (see below) before and after the import to check nothing was lost.
What is Migration Verify and how does it work?
Before you import from another SEO plugin, open Livada SEO → Migration Verify, tick the pages you want to check (the home page, a static front page, the pages carrying the other plugin's data and your latest posts are listed; you can also type any address of your site) and click Take the before snapshot. The plugin reads each live page the way a search engine does and saves its head tags (title, meta description, canonical, robots, Open Graph, JSON-LD). After the import, click Compare with the snapshot: for each page, each tag is shown as Unchanged, Changed (still there, different text), Missing (was published, now gone) or Added, with the before and after values side by side, and a tag that is now published twice is flagged too. Reworded text is not an error; a missing tag is. The same checks are available through the REST API and the WordPress Abilities API.
How does the AI suggestion feature work?
Add an API key for Anthropic, OpenAI or Google Gemini under Livada SEO → General and choose the provider. The AI ✨ buttons in the SEO box then ask that provider for a title, a meta description or a focus keyword and put the answer in the field, where you can edit it before saving. Anyone who can edit a post can use these buttons, and the requests use your key. See "External services" for exactly what is sent.
Where is my API key stored?
In your WordPress database, in the plugin's settings option. When PHP's OpenSSL extension is available it is encrypted with AES-256, using a key derived from your WordPress salts (wp_salt( 'auth' )); without OpenSSL it is only base64-encoded. This keeps the key out of plain sight in a database export, but it does not protect it from someone who can read both your database and wp-config.php. An encrypted key can only be read back with the same WordPress authentication salts (AUTH_KEY and AUTH_SALT) and PHP's OpenSSL extension: after you change them, or move the database to another site or to a server without OpenSSL, the AI features stop working until you enter the key again. Use a key limited to what you need, with a spending limit, and tick Remove saved key under Livada SEO → General if you stop using the feature.
What's the difference between this and Livada SEO Pro?
Same underlying SEO data (titles, descriptions, business info) — Pro adds advanced features on top: multiple business locations, automatic image optimisation, hreflang, WooCommerce, Site Audit and bulk tools. They are two separate plugins; nothing in this plugin is disabled or time-limited.
How do I move from Livada SEO Lite to the full Livada SEO plugin without losing anything?
In this order:
- Install the full Livada SEO plugin (livada.io/livada-seo). The two cannot run at the same time, so deactivate Lite first (keep it installed: deactivating deletes nothing), then activate the full plugin.
- In Livada SEO → Tools of the full plugin, run Import from Livada SEO Lite (the full plugin also offers it in a notice). It copies the site-wide settings; per-post SEO data, redirects and the 404 log are stored in the same place by both plugins and are shared automatically.
- Enter your AI provider API key again in the full plugin: it is not copied. Your AEO settings are copied by the full plugin from version 1.53.11; with an older version, re-enter them under its settings.
- Only then delete Lite.
How do I uninstall cleanly?
Use Plugins → Delete. uninstall.php removes the plugin's options (including its settings and any saved API keys), every post meta with the _livada_seo_ prefix, the redirects, 404-log and activity-log database tables, and the plugin's transients. If Livada SEO Pro is installed, active or not, nothing is deleted, not even this plugin's settings and API keys, because Pro uses the same data. On a multisite network it only cleans the site it runs on; other sites keep their data.
更新日志:
1.1.9
- Improved: the sitemap built into WordPress (/wp-sitemap.xml) is switched off, since the plugin provides its own, as other SEO plugins do. It did not follow your "noindex" and "exclude from sitemap" choices and also listed author accounts and page-builder templates; now search engines are offered one sitemap, the one that respects your settings.
- Improved: old addresses of the WordPress sitemap (/wp-sitemap.xml and its sub-sitemaps) now lead to the plugin's sitemap (/sitemap.xml, or /?livada_sitemap=index with plain permalinks) with a permanent redirect, so a search console that still knows them finds the right one. If a page cache stored /wp-sitemap.xml before the update, clear it once.
- Fixed: /sitemap.xml followed by a query string is no longer redirected to an address ending in a slash.
- Fixed: the business description keeps encoded characters such as %C3%A9 when saved.
- Fixed: on the Migration Verify screen, a page title containing "&" or a typographic apostrophe showed its code (for example
&) instead of the character. Titles now read normally. - Fixed: the 404 log table and the redirects table are now created when the plugin is activated. A page or a 404 served right after an activation through WP-CLI or a bulk tool no longer meets a missing table.
- Fixed: when "Discourage search engines from indexing this site" is ticked under Settings > Reading, the plugin still published its XML sitemap and
/llms.txt(a list of your pages for AI assistants) and replaced WordPress's robots.txt with its own, which carries a Sitemap line. WordPress's own robots.txt is now kept, and the sitemap and/llms.txtare no longer published while the box is ticked. - Improved: the notice on the General screen now says to add business details (name, address, phone or email), since any of them is enough.
- Tested up to WordPress 7.1.2.
- Fixed: the REST API now checks the type of each setting. A switch sent as a list, a decimal or a JSON object (for example
["false"]) was stored as is and read as on; a single-value setting (a URL, a name) could be stored as a list; a list setting (post types, sameAs, topics) could be stored as one string; a nested list inschema_same_ascaused a fatal error on PHP 8. Each is now ignored or cleaned, and an empty value clears a list. - Fixed: through the REST API, the founding year accepted any text and could reach the business schema. It now takes four digits, like the settings form.
- Fixed: the "Nothing is published yet" notice no longer shows while AEO itself is switched off.
- Fixed: a content type set to noindex under Titles (for example all pages) was still listed in
/llms.txt. It is now left out, as a single noindex page already was. - Fixed: sending a switch such as
aeo_knowledge_graphas the text "false" through the REST API turned it on. "false", "0" and "off" now switch it off. - Improved: when business details for AI are ticked but no business name is set, the General screen now says nothing is published yet, instead of staying silent.
- Added: AEO for AI assistants, free.
/llms.txtand/llms-full.txtsummarise your business and link to your main pages; a business description, founding date, founder and areas of expertise are added to the business entity your Schema settings already publish (one entity, never a second one);max-snippet:-1,max-image-preview:largeandmax-video-preview:-1are added to the robots meta tag and sent as anX-Robots-Tagheader, never on a page set to noindex; optional meta tags and content markers. Every part can be switched off under Livada SEO → General, section AEO. Nothing is sent to any service. - Added: an admin screen for Migration Verify under Livada SEO → Migration Verify. Tick the pages to check (or type an address of your site, including a home page that lists your latest posts), take the before snapshot, run your import, then compare: each tag is shown as Unchanged, Changed, Missing or Added. It was previously reachable only through the REST API and the Abilities API.
- Improved: the Tools screen points to Migration Verify before an import, and the dashboard links to it.
- Improved: the readme explains how to move to the full Livada SEO plugin without losing data.
- Fixed: importing from Yoast SEO, Rank Math, SEOPress or All in One SEO failed with a fatal error, because a file the importers need was missing from the plugin package. It is now included.
- Fixed: the SEOPress redirect import turned temporary (307) and other non-301/302 redirects into permanent 301 redirects. Only 301 and 302 redirects are imported now; the others are skipped and counted, as the other importers already did.
- Fixed: the Import from … buttons under Livada SEO → Tools copied posts only. They now also copy the other plugin's redirects and show the notices the import reports. They no longer stop at "Nothing to import." when no post carries data, which also skipped the site-wide settings, and they can be clicked again after a failed request.
- Fixed: importing redirects a second time, or adding a redirect whose source already exists, triggered a database error. On a site with debugging switched on it was printed on screen and made the import screen report a failure. The duplicate is now skipped quietly and counted as skipped.
- Fixed: the Yoast SEO and Rank Math imports never replaced this plugin's default title templates with yours, because the defaults written at activation counted as values you had set. A template you changed here is still kept. Their site-description and archive-name variables are now converted too, and a template that uses a variable this plugin does not have is not copied: the import result names it, instead of your pages showing the variable as text.
- Fixed: a noindex or nofollow you set by hand in a post's SEO box can no longer be cleared by a later import that has no opinion about that page.
- Fixed: the REST API and the Abilities API listed routes and abilities that belong to Livada SEO Pro (WooCommerce product schema, Site Audit, IndexNow, AI bot access checks) and could not work in this plugin. They are no longer registered here. The IndexNow route also answered "scheduled" although nothing was listening.
- Fixed: an empty Agent Skills index was published at
/.well-known/agent-skills/index.json. It is no longer published, and/auth.mdno longer points to it. - Fixed: the WordPress.org description and readme announced an "AI visibility score" and an Elementor dynamic tag that this plugin does not provide, and listed Migration Verify without saying it has no admin screen (it is available through the REST API and the Abilities API). They now describe only what the plugin does. The AI Visibility Score module is not reachable from the admin in this version.
- Fixed: the MCP Server Card (
/.well-known/mcp/server-card.json) described features of the paid plugin. It now describes this plugin, and on WordPress versions before 6.9, which have no Abilities API, it no longer refers to that API or to an MCP adapter. - Fixed: Migration Verify stored its "before" snapshot with its escaping stripped. A page with accented characters in its tags was wrongly reported as changed, and a page with quotation marks failed with "snapshot unreadable". Snapshots taken with earlier versions are not repaired: take a new one.
- Fixed: the breadcrumbs stylesheet (
assets/css/breadcrumbs.css) was requested but missing from the package. - Fixed:
sitemap.xmlreferenced a stylesheet that was not shipped, which made some browsers show a blank page. The reference is removed; search engines were never affected. - Fixed: the dashboard said Livada SEO Pro adds redirects and a 404 monitor. Both have been free in this plugin since 1.1.0.
- Fixed: the link to the General settings in the Image SEO screen led to a page that does not exist.
- Fixed: the buttons of the Image SEO and Activity Log screens did nothing, because the script that drives them was never loaded on those two screens. It is now, so Save, AI suggest, Apply and Clear log work.
- Fixed:
%category%and%date%in your title and description templates were damaged when saved (WordPress's text filter deletes what looks like a URL-encoded character,%cain%category%and%dain%date%, so they were stored astegory%andte%). They are now kept by the Titles & Metas screen, the SEO box, the REST API and the importers. Templates already damaged by an earlier version are repaired once, at the update, including two variables written back to back (%title%%date%). Only the site-wide templates are repaired: a title or description you typed with%category%or%date%in one post's SEO box while an earlier version was installed has to be typed again. - Fixed: a description written for one post, or for the home page, showed its variables as text (for example
%sitename%) in the meta description, the Open Graph description and the Article schema. They are now replaced there, as they already were in titles, and markup is stripped from them as in the meta description. - Fixed: an API key saved through the REST API or the Abilities API was stored as plain text, and reading the settings returned it. It is now encrypted like a key saved in the admin, and the REST API and the Abilities API only say whether a key is set. A key that an earlier version stored as plain text is encrypted once, at the update. An empty key value sent to the REST API now leaves the stored key unchanged, so a script that sends back what it read no longer erases it; to remove a key, send
anthropic_api_key_clear,openai_api_key_clearorgemini_api_key_clearset totrue. - Fixed: saving settings through the REST API joined a multi-line
robots.txtinto one line and emptied list settings such asschema_services. They are kept as sent. - Fixed: saving
robots.txt, in the admin or through the REST API, deleted every URL-encoded character (%C3%A9,%20...):Disallow: /r%C3%A9servation/becameDisallow: /rservation/, and a rule made only of such characters becameDisallow: /, which blocks the whole site. Those characters are now kept. Arobots.txtsaved that way by an earlier version is not repaired: check yours under Livada SEO → Robots.txt. - Fixed: Migration Verify and the Markdown check could follow a redirect from a page of your site to another domain and fetch it from your server. They now stop at any redirect that leaves your site.
- Fixed: the Open Graph
og:localetag was alwaysfr_FR. It now follows your site language. - Fixed: AI alt-text suggestions sent the model name chosen for OpenAI or Gemini to Anthropic when one of those was your AI provider, so the request failed. They now always use an Anthropic model.
- Fixed: on a server without PHP's OpenSSL extension, a saved API key could not be read back and the AI features reported a missing key. The key is now kept base64-encoded there and works; it is encrypted whenever OpenSSL is available.
- Fixed: the breadcrumbs navigation label was always in French. It is now translatable and reads "Breadcrumb" by default.
- Fixed: when the discovery files (API catalog, MCP server card,
/auth.md) were switched off, the rewrite rules registered by earlier releases were never cleaned up and could keep answering with your home page. They are dropped at the update. - Removed: an AI "rewrite" mode and a FAQ-generation action that no button in the admin used, so that the only AI requests the plugin can make are the ones listed under External services.
- Fixed: "Plugins → Delete" left the Activity Log table and some internal options behind. It now removes them too. Nothing is deleted while Livada SEO Pro, which shares this data, is installed.
- Improved: the readme and the plugin's own texts no longer overstate what the plugin does. The on-page checks are recalculated when you save (they are not live), AI alt-text suggestions use Anthropic only, and the API key is encrypted with a key derived from your site's salts (base64 only when OpenSSL is missing). The External services section lists exactly what is sent, and a Privacy section and the list of files the plugin publishes were added.
- Improved: the on-page analysis is described with its real number of checks (20), and the readme tags are limited to the five WordPress.org uses.
- Improved: the requests Migration Verify makes to your own site follow WordPress's own
https_local_ssl_verifyfilter (off by default, as before).
- Improved: the MCP Server Card now also states its name, version, description, server URL and (empty) tools list at the top level, so more agent-readiness checkers can read it. Same true values as before; no new claim and no new endpoint.
- Improved: plugin description and tags on WordPress.org better reflect the real differentiator (Campground/Hotel/B&B/Restaurant schema, migration verification, AI visibility score). No functional or code change.
- Added: Redirects & 404 Monitor, now free — 301/302 redirects with regex support, CSV import/export, and a 404 log you can convert into redirects in one click. Matches what Livada SEO Pro already offers for free, closing the gap with other free SEO plugins that already include this.
- Initial release: meta, sitemap, schema, Open Graph, breadcrumbs, on-page analysis, robots.txt, AI suggestions, image alt-text review, and importers for Yoast/Rank Math/AIOSEO/SEOPress.