SEOYEN SEO Platform -- WordPress 插件

开发者	seoyen tevfikgulep
更新时间	2026年9月11日 06:02
PHP版本:	7.4 及以上
WordPress版本:	7.1
版权:	GPLv2 or later
版权网址:	版权信息

2.2.8

Fixes that said "applied" while a third-party SEO plugin was active now tell the truth. With Yoast, AIOSEO, Rank Math or SEOPress installed, og:type, og:url, twitter:card and hreflang were written only to this plugin's own storage and never rendered on the page — yet the endpoint reported success and the panel closed the issue. They now report honestly as not applied, and the issue stays in your report.
"Links to a redirect" now fixes http:// → https:// and non-www → www links — the most common redirects on a WordPress site; the fix was skipping every one of them as "nothing to change".
Schema fixes accept LocalBusiness subtypes (Hotel, Restaurant, Store, clinics…); the gate accepted only the exact LocalBusiness type. Unrelated types are still rejected.
Broken outgoing link fixes no longer report three skipped outcomes as success (external target, self redirect, redirect rule could not be created), and every skipped fix now explains why.
An invalid Twitter card type no longer leaves a half-written post — validation runs before anything is written. An invalid schema mode is rejected instead of silently falling back to append and duplicating a graph node.
Failed saves no longer say "Settings saved." Write failures were swallowed on the Settings, Companion, setup-wizard and Google Indexing screens (API key included); you now see which setting failed. The Site Status "Refresh" button no longer fails silently for users without permission or with an expired security check.
When the panel refuses to save a setting, its reason is shown (a plan limit, for example) instead of "could not reach the panel"; warnings the panel returns with a save are no longer swallowed; and settings that failed to write on your own site (database or object cache) are reported separately from the panel's rejections.
The SiteSEO and robots.txt conflict warnings never reached the screen — the plugin's own "suppress foreign notices" sweep removed them; both re-register after the sweep and are actually shown now.
Suggestions screen. "Apply to WP" is printed only for the five types the endpoint can write to your site (measured: 3,354 of 3,447 pending suggestions — 97.3% — returned an error on click); the bulk-fix confirmation now says fixes are applied automatically; publishing the same article twice no longer creates a second draft; applied or rejected suggestions leave the list immediately instead of an hour later; an unreachable panel shows the error and a retry button instead of "no issues to fix".
A failed IndexNow ping no longer marks the post as reported for an hour — failures are recorded and retried on the next save. Sites without Google Indexing permission no longer wait 15 seconds on every post save — a permanent authorisation error backs off for an hour and clears itself once access is granted.
No more scheduled jobs on your site; the panel pulls the data. The three WP-cron jobs (daily telemetry, hourly AI-crawler hit push, daily activity-log pruning) are gone — WP-cron never runs on a site with no visitors and makes a visitor wait on a busy one. Leftover schedules are cleared on upgrade and the Site Status screen says so. Counters are marked as sent only after the panel has actually received them, so a half-finished delivery is retried and the same day is never counted twice. The "Send hits now" button stays as the escape hatch for installs the panel cannot reach; on installs that never connected, the AI-crawler buffer is pruned daily.
Maintenance actions live on the Dashboard — sync with the panel, send AI-crawler hits, write redirect counters, clear the plugin cache, refresh virtual URLs: five local actions with buttons, folded into the Dashboard instead of taking a separate menu page.
A brief panel hiccup no longer strands a screen behind "HTTP 500". When the panel is momentarily unreachable a shared 180-second breaker opens so screens don't hang; but "Retry" cleared only the local lock, hit the still-open breaker and returned HTTP 500 ("unexpected response"). Retry now resets the shared breaker too, and temporary failures return 503 ("try again"), not 500.
Page-builder gate. On pages built with Elementor, WPBakery, Divi, Beaver Builder or Oxygen the post_content field is a stale copy; body-writing fixes, paragraph insertion and internal links now detect the builder and report honestly that the fix must be applied inside the builder editor (seoyen_page_builder_owner filter).
The string "false" no longer counts as true on REST endpoints (noindex, physical robots.txt, llms.txt enabled, redirect is_active); an unrecognised boolean returns 400 before anything is written.
Fewer queries per page view. Redirect rule lists now survive between requests (two queries per view even with an empty rule table) and are dropped the moment a rule changes — if the carrier cannot be read the query runs as before, so your redirects never go quiet; two queries removed on sites whose theme prints its own description; option defaults are seeded autoloaded on upgrade, the post-activation rewrite flag is reset instead of deleted, and the bot-signature catalog reads the persistent record first (three more).
Content Bot. The minimum run interval is plan-based — 10 minutes on Enterprise, 30 elsewhere — with floor and step from the panel and no local clamp, while the hint under the box keeps naming the standard 30-minute minimum (a single article takes ~15 minutes on average and up to ~37, so 10 is an Enterprise exception, not a recommendation); the wizard reports when its done flag cannot be written; "Open post" titles no longer show ’; countable strings use proper plurals; status-strip stamps use the same site-time reader as the run table; the Search Console connect link passes the scheme filter.
Publishing and admin endpoints: 25 MB cap and image MIME check on featured-image downloads; bulk alt-text reports failed items; Google Indexing last-URL stamp verified; bulk redirect import emits a seoyen_redirects_imported webhook event; schema mode is a closed set at the write site too; skipped term fixes carry their reason in hint; the plugin advertises which suggestion types it can write (apply_tool_ids) so the panel no longer guesses from the version.
Multisite and uninstall: the six plugin tables are dropped with wpmu_drop_tables when a network site is deleted; the network install queue, a user-meta key and an owner override option are cleaned on uninstall; the post-upgrade version announcement uses a 5-second timeout; activation sends home_url() on subdirectory installs.
Security: a panel-supplied link was printed without validation on three admin surfaces, including the Content Bot wizard's Search Console link (only http/https pass now), and admin assets loaded on foreign plugin pages whose slug started with seoyen (exact screen match now).

2.2.7

Site-wide SEO: all eight tabs now actually do something. The screen shipped with eight tabs, but only the separator, the title patterns and a few social/schema keys were ever read — ticking "disable author archives", "Google verification code", "remove emoji scripts", "RSS prefix" or "breadcrumbs" said "saved" and changed nothing on your site. Robots, crawl cleanup, structured data (WebSite, knowledge graph, per-type Article/BlogPosting, real @id linking) and breadcrumbs ([seoyen_breadcrumbs] shortcode and seoyen_breadcrumbs() template tag) are all applied now, and the visible breadcrumb trail and the one reported to search engines finally come from one source.
Readable {token} syntax in patterns. {title} {sep} {sitename} replaces %%title%% %%sep%% %%sitename%%; existing records migrate on their own and both forms keep resolving. An unrecognised token is rejected when you save and reported to you instead of leaking into your page title, and a token sitting inside a resolved value is no longer resolved a second time or silently deleted.
The same settings live in wp-admin, and both screens show the same values. The tree is built from your site's real post types and taxonomies instead of nine fixed ones, with a per-language override layer. Empty fields arrive with recommendations — ready patterns with your brand written as {sitename} rather than baked in, and your real site name pulled in so the length counter is honest. A recommendation is not a default: nothing changes on your site until you save, and the screen says so.
Every tab, section and key now explains itself, limits included ("removing the REST link does not disable the REST API itself"). The variable table gained an "example on your site" column, and image fields get a real WordPress media picker with a preview.
Suggestions start with site-wide fixes, and the payoff is measured. Above the tab bar you now see how many issues and rules each group holds and, when it can be measured, "one change closes N issues" — measured on a 1,672-page site, a single title-pattern change closes 1,246 of 1,286 "title too long" issues. The number is computed from your last audit run and nothing is printed when it cannot be measured. Each group deep-links to its tab, where apply-and-save takes one click and writes only the fields you applied. Per-page suggestions were not removed.
Security: your Google Instant Indexing service-account key is now encrypted at rest. The JSON, private key included, was stored in plain text, so a database dump or any plugin that lists options could expose it. It is now kept in an AES-256-GCM envelope whose key is derived from your wp-config.php salts and never stored. Existing installs migrate on first read; if the envelope cannot be opened after a salt change or a server move you are told to re-upload the JSON instead of seeing a silent "not connected".
Security: the ReDoS gate catches five more bypass classes and the failed-key counter is race-free. Grouping layers (((a+))+), ambiguous alternation ((a|aa)+) and the spaced x form (/^( a + ) + $/x) were all accepted before at the same cost, and on servers with an unlimited PCRE backtrack limit the clamp was skipped exactly where it mattered (measured: 15 seconds for one rule). The bucket counting bad API-key attempts used read-modify-write, so concurrent requests multiplied the per-minute limit, and the 250 ms delay was paid before the counter moved.
"Applied" is only reported when something was really applied — eleven paths closed. The plugin used to answer "written" while nothing changed on your site: your audit issue was stamped resolved and AI credit was spent. Content writes are now read back and compared; a missing anchor no longer appends the paragraph to the end of the post; a physical robots.txt shadowing the virtual one returns an explicit error instead of 200; invalid og:type, og:url, twitter:card and review ratings never reach storage; the same paragraph is not written twice; "nothing changed" no longer fires your webhook; term fixes go through the same gate as post fixes; and a failed callback to the panel is now shown instead of "✓ Fixed".
Redirect loops are caught across the whole chain. A → B → C → A made pages unreachable with ERR_TOO_MANY_REDIRECTS: only a single step was checked, and editing an existing rule's target skipped the gate entirely. Create and update now share one gate that walks the chain. Bulk import no longer accepts fields outside the contract, an already-inactive rule is not counted as "1 hop removed", and resolving a chain appends to your note instead of overwriting it.
Front end: share cards, canonical, structured data and robots.txt. A SEO title now reaches og:title/twitter:title; a card is no longer left without a description; both cards use the same image; the site-wide pattern no longer overwrites a post's own social title or description; and a canonical you wrote is really applied when the theme printed its own first. Raw HTML entities are gone from JSON-LD across 27 fields (measured live: Türkiye'nin) while address and identity fields stay untouched, @graph members no longer carry @context, and variable WooCommerce products are reported with AggregateOffer instead of a single lowest price. Unticking "Output native meta tags" no longer leaves titles, robots, schema, breadcrumbs and redirects unbound or deletes our own schema nodes, and removing one bot from robots.txt no longer deletes another bot's shared Disallow: or migrates rules into the wrong group.
Content writes no longer damage what they touch. An internal link for the anchor SEO was written as <a href="…">SEO</a>YEN, splitting a brand name in your published body with no way back — and in the other direction an unlinked phrase was skipped as "already linked". Both gates now share one Unicode word-boundary grammar (required for Turkish). Separately, an update from the panel no longer silently demotes a published post to draft: unknown statuses are rejected, and statuses your own site registers (archived) are kept.
Screens, AIOSEO and the commerce ledger. You now come back to the tab you saved; CSV import counts the rows it drops instead of reporting a clean success; the dashboard widget and System Status no longer contradict each other; bulk delete without JavaScript explains itself instead of doing nothing; and Content Bot run history speaks in your site's time, including runs created after midnight. With AIOSEO active, term fixes are now really written and verified or honestly skipped, and "improve this meta description" can see your existing text. In the ledger, a failed journal write no longer loses a price change and a 5,000-row backlog no longer locks it permanently. Also: resumable multisite activation, backoff on hosts without table-creation rights, RSS tokens resolved per post, "Page 2 of 1", static front pages, sub-directory path doubling, meta description cleanup, and bulk requests consuming their real rate-limit weight.

2.2.6

Anchor links (#…) can now be fixed. The "links to a redirect" fix could not find a link that carried a section anchor (/privacy-policy/#your-rights): it answered "this may come from a theme template, fix it by hand" while the link was right there in the page body (measured on the live site). Matching now ignores the anchor and carries it over to the new address: /privacy-policy/#your-rights → /privacy/#your-rights. If the destination the panel measured carries an anchor of its own, that one wins; links without an anchor behave exactly as before.
A page no longer links to itself. WordPress's "guessed redirect" feature 301s a made-up or stale short URL to the very same post most of the time. The fix took that for a "new destination" and rewrote the link to the page's own address: a pointless link that also hid the real problem (the made-up URL). Such a pair is now never applied — the panel does not send it and the plugin does not write it; the reason is stated in the response and you are asked to fix or remove the link by hand.

2.2.5

"Links to a redirect" is now actually fixed in your content. The audit finding used to be wired to the wrong fix: the plugin wrote a 301 rule while the <a href> on the page stayed unchanged, so the issue came straight back on the next crawl (and most calls failed outright because the panel could not produce the data that fix needed). The link on the page is now rewritten to the final destination the panel measured live, and your markup style is preserved — a relative link stays relative. If the link lives in a custom menu item instead of the post body, the menu URL is updated and read back to verify the write.
What is left alone is stated plainly. A link whose final destination is another site is never rewritten (it may be intentional), and links the panel could not measure (timeout, loop, non-2xx response) are skipped with the reason in the response. www. and non-www. addresses are treated as different targets — that difference is the defect being fixed.
"Fixed" is only reported when something was actually fixed. When an audit fix could not be applied (the URL matches no post, the link comes from a theme template, the target is external) the plugin still answered success: the activity log recorded success, the seoyen_audit_applied event — and therefore your webhook — fired, and the row in wp-admin was marked "✓ Fixed". Such a result is now logged as skipped, the webhook does not fire, the row is not marked fixed, and the reason is shown on screen. The same contract was closed on the internal-link endpoint in 2.2.4; the audit endpoint was still open.
Automatic "Table of Contents" insertion has been removed. Fixing an audit issue from the panel or the plugin no longer prepends a table of contents to your post. A table of contents is a design component, not SEO data: the generated list was an unstyled flat <ul>, ignored heading levels, and was written permanently to the top of the post with no way back. Detection stays: the "no table of contents" finding is still reported — solve it with your theme's or a dedicated plugin's own component. The content-editing mode list is down from six to five (append, replace, add_subheadings, split_paragraphs, simplify_sentences); the removed add_toc mode is now rejected explicitly.
The "paragraph too long" fix no longer burns AI credit for nothing. That fix splits paragraphs entirely locally, at sentence boundaries in your own text — it never looked at the AI output. The panel still generated text on every click, charged your credit and threw the result away. AI is no longer called for this fix and no credit is spent. The split threshold now matches the audit's own threshold (300 words); previously the plugin's 120-word default was used and paragraphs that were never flagged got split too.

2.2.4

The Content Bot's "Run now" no longer publishes the same post twice. The panel already published the post when the run finished; the plugin didn't know that and created the same article a second time. The panel now publishes and the plugin only shows an "Open post / Open draft" link; a "Push to draft" button appears only if the panel could not publish.
wp-admin no longer waits 20 seconds when the panel is unreachable. Suggestions, Internal Link Suggestions and the SEOYEN data pages never got the 5-second cap promised in 2.2.3, and each of four independent hooks paid its own timeout. All panel calls now share one circuit breaker capped at 5 seconds, a failure is remembered for 15 minutes with a "Try again" button, and "Test Connection" always bypasses the circuit for a real request.
The "Connected" badge now reports the panel's own verdict — it shows "Not verified" with a link to the wizard when the panel has rejected your API key, instead of reading "Connected" merely because a key is present.
Changing the API key or panel URL now clears the plugin's cache, including on sites with a persistent object cache, and "Reset All Settings" also drops runtime records and stale keys — previously data belonging to the old key survived the change.
Redirects now match the requests they were meant to match: an exact-match rule also catches requests carrying query strings (?utm_source=…, ?fbclid=…), percent-encoded requests match rules written with Turkish characters, a prefix rule whose target sits under its own source no longer loops, and a bulk import above 500 rows is rejected explicitly instead of being silently truncated.
The write path is honest: Twitter Card, review fields, noindex removal, site-wide settings and schema deletion are no longer reported "applied" without a verified write; "internal link applied" is reported only when the link was really inserted (a skipped result is logged as skipped, with a reason, and fires no webhook); writing llms-full.txt no longer returns an unverified 2xx; sending the same article twice returns the existing post instead of creating a second one; and an appended paragraph no longer lands inside a Gutenberg heading block.

2.2.3

Security. A pattern (regex) redirect's target could put the part captured from the pattern into the domain of the destination address (https://$1) — an open door that could send a visitor to a completely foreign site based on what they typed. Such a target is now rejected on save and, even if one was saved earlier, is never applied at request time; using $1 in the path still works. Your IndexNow key — IndexNow's proof of ownership for your site — is now served only from its own path instead of being readable from any address on your site.
Uninstalling no longer leaves data behind. With "delete data too" selected, all six tables the plugin creates are now dropped (2.2.2's removal list was hand-written and only counted four), along with _seoyen_* fields on categories and tags, the plugin's own user preferences, three forgotten option rows, five transient families and a leftover scheduler. On multisite networks every site is now walked individually and each follows its own "keep my data" preference; Yoast / Rank Math / SEOPress fields are left untouched.
"Applied" lies are closed, and panel-driven fixes no longer damage your content. Canonical, hreflang, og:type, og:url, twitter:card, image alt text, llms-full.txt and writes to a third-party SEO plugin now require a verified write before success is claimed. Re-saving a post through a panel-applied fix used to permanently remove manually-added <iframe> (YouTube embeds, maps), <object> and <script> elements — your existing content is now preserved as-is. Internal-link insertion is scoped to visible text only, so an anchor word that also appears inside an alt= attribute or a Gutenberg block comment no longer breaks the image or the block.
wp-admin no longer freezes for 20 seconds when the panel is unreachable (calls capped at 5 seconds, a failure remembered for 15 minutes), and SEOPress and All in One SEO are now detected correctly — with either plugin active SEOYEN kept printing its own meta/OG/Twitter/canonical tags on top of theirs, and now stays quiet. Your saved data is not deleted; it all comes back if you deactivate the other plugin.

2.2.2

The "Duplicate H1" and "H1 too long" fixes can now actually be applied. For these two findings, "Apply via WP" changed nothing on most themes: the plugin could only fix the <h1> tag in the post content, while most themes print the visible heading from the post title, not the content. Measured (28 August 2026, three rounds): the target posts had no <h1> in their content at all, the fix was silently skipped all three rounds, and the same finding kept coming back on every audit.
You're now explicitly asked what should happen. If there's no <h1> in the content to change, the plugin no longer gives up silently; the panel shows a "Also update the post title" checkbox under the fix. Nothing changes unless the box is checked.
Your permalink never changes. Once you approve, only the post title is updated — the permalink (slug) stays exactly as it was. Where the title appears: menus, post lists, and search results.
No "I did it" lie. If WordPress rejects the title update, the fix is not counted as successful; the issue stays open in the audit list.

2.2.1

Meta descriptions reported as "fixed" now actually show up on the page. Six fix types replied "written" and genuinely saved the value, but nothing changed on the page the visitor saw. MEASURED (live, 28 August 2026; 18 fix types × 3 rounds): content.meta_too_long, content.meta_too_short, content.meta_description_duplicate, and social_meta.og_description_missing stayed silent 3/3 rounds.
Cause: the plugin saw "this tag already exists on the page" and backed off. Most themes print their own <meta name="description"> tag before the plugin's turn comes. This wasn't specific to any one site — every site whose theme prints its own description had the same silent no-op.
Now: if you have an explicitly saved value, the plugin REPLACES the existing tag instead of staying quiet — covers the page description, Open Graph description and type, and Twitter Card type/title/description.
Deliberately left alone: if the value isn't text you wrote but a fallback derived from an excerpt, the theme's tag is untouched; if Yoast / Rank Math / SEOPress / AIOSEO is active, nothing changes; if multiple tags share the same name, only the first is fixed.
twitter:card is no longer duplicated — if the theme (or a plugin like Jetpack) already prints its own card tag, a second, conflicting one is no longer added. All three output points in the class now follow the same contract.
Whether the overwrite happens or is skipped, a descriptive line is written to the server error log at most once an hour.

2.2.0

Eleven labels that had stayed in English on the Turkish admin screen were translated — tool names (Meta Description, Alt Text, Social Media Converter, Paragraph Generator, Auto-Fix), severity levels (Critical, Info), and article-card labels (AI Article, Keyword:, Draft, Published). The same screen no longer mixes two languages.
Only the displayed text changed; settings, records, and the technical post-status values (draft / publish) stayed the same.

2.1.3

"Tek Tıkla Düzelt" artık gerçekten hepsini kapsıyor. Kart "42 URL etkilendi" derken düğme yalnız ekranda gösterilen ilk 5 adresi düzeltiyordu. Düğme artık ekrandaki listeye hiç bakmaz: sorunun TÜM uygun adreslerini panelin toplu düzeltme motoruna verir.
Tıklamadan önce ne harcayacağınız yazılı olarak söyleniyor — kaç sayfa işlenecek, tahmini kaç kredi gidecek, kalan bakiyeniz ne. Onaylamadan hiçbir kredi harcanmaz. Bakiye sınırsızsa rakam yerine "sınırsız" yazar; maliyet hesaplanamıyorsa uydurulmaz, "hesaplanamadı" denir ve sayfa sayısı yine söylenir.
Kart, panelin o soruna ait sayfasına bağlantı veriyor ("Tek tek seçmek için panelde aç →") — hangi sayfayı düzelteceğinize tek tek karar vermek isterseniz oradan seçersiniz.
İlerleme dürüst üç kovada gösteriliyor: hazır · hata · bekliyor. "Bekliyor" hata değildir — o adresin düzeltmesi henüz üretilmedi. İstediğiniz an durdurabilirsiniz; durdurmak izlemeyi keser, panelde süren üretimi öldürmez ve bu açıkça yazar.
Etkilenen adres önizlemesi 5 yerine 20 satır gösteriyor.

2.1.2

Düzelttiğiniz denetim sorunları aktif listeden düşüyor. Bir sorunu düzeltmenize rağmen kart listede duruyordu; hangi işi yapıp hangisini yapmadığınızı ayırt edemiyordunuz. Düzeltilenler artık "Uygulanmış düzeltmeler" başlıklı, varsayılan olarak kapalı bir bölümde toplanır — kaybolmazlar, sadece yolunuzdan çekilirler.
Bir sorun yeniden ortaya çıkarsa kendiliğinden aktif listeye döner — arşiv "bir daha bakma" listesi değildir; sonraki denetimde aynı kontrol yeniden başarısız olursa sorun açık listede yeniden belirir.
Uygulanmış düzeltme sayısı başlıkta gösterilir; sayı panelden okunamıyorsa başlık sayısız basılır, uydurma rakam gösterilmez.

2.1.1

"Uygulanıyor…" sonsuza kadar durmuyor — düzeltme ekranı bir sonucu iki saate kadar bekleyebiliyordu; geçen süre yoktu, iptal yoktu. Bekleme artık ölçülmüş süreye göre: tek düzeltme için 6 dakika, bir sorunun tüm adresleri için toplam 30 dakika.
Beklerken geçen süre görünüyor ("42 sn", "3 dk 07 sn") ve istediğiniz an İptal diyebiliyorsunuz. İptal dürüsttür: izleme durur, sunucudaki üretim arka planda sürebilir, ama sitenize hiçbir şey yazılmaz — yeniden deneyebilirsiniz.
Süre dolduğunda "başarısız" denmiyor — düzeltme hâlâ üretiliyor olabilir; ekran "sonucu bekleyemedik" der ve ne yapmanız gerektiğini yazar.
"Ağ hatası" yerine sunucunun gerçekten ne dediği yazıyor — zaman aşımı mı, sunucuya ulaşılamıyor mu, beklenmeyen yanıt mı; durum koduyla birlikte. Ham hata sayfası kullanıcıya gösterilmez, yalnız geliştirici konsoluna düşer.

SEOYEN SEO Platform

标签

下载

详情介绍:

安装:

屏幕截图:

升级注意事项:

常见问题:

更新日志: