[WordPress] 外掛分享: Megop SEO – Bulk Editor, Internal Links, Broken Links & Search Console

首頁外掛目錄 › Megop SEO – Bulk Editor, Internal Links, Broken Links & Search Console
WordPress 外掛 Megop SEO – Bulk Editor, Internal Links, Broken Links & Search Console 的封面圖片
10+
安裝啟用
★★★★★
5/5 分(1 則評價)
9 天前
最後更新
問題解決
WordPress 6.0+ PHP 7.4+ v8.3.0 上架:2026-09-03

外掛標籤

開發者團隊

⬇ 下載最新版 (v8.3.0) 或搜尋安裝

① 下載 ZIP → 後台「外掛 › 安裝外掛 › 上傳外掛」
② 後台搜尋「Megop SEO – Bulk Editor, Internal Links, Broken Links & Search Console」→ 直接安裝(推薦)
📦 歷史版本下載

原文外掛簡介

Internal linking on WordPress is a paid category. The tools people recommend are commercial and closed source, their licences are proprietary, and the ones that publish a price ask anywhere from a monthly subscription to several hundred dollars. All of them were built for English first. The most translated of them ships a dozen interface languages, and Persian is not one of them.
So for a Persian site the shelf has been empty. Not a free option, not an open one, and not one that knows a Persian phrase can be spelled four ways that look identical to a reader and are four different strings to a computer.
This is the option that was missing. GPLv2, every line. Five tools that would normally be five purchases, sharing one index so they agree with each other instead of fighting.
If you have been looking for a bulk editor, a bulk price editor for WooCommerce, a bulk duplicator, a search and replace tool, a redirect chain checker or a self hosted analytics plugin, five of those are here, in one plugin, free.
Written and maintained by محمد قاسمی (Mohammad Ghasemi), Tehran, Iran.
Seo Bulk Manager: your whole site in one grid
Every public post type and every public taxonomy, whatever registered them. Posts, pages, WooCommerce products, product categories, a custom post type a plugin created this morning. Nothing is hard coded and nothing is special cased.
Edit the row, not the page. H1, SEO title, meta description, featured image, status, category, term parent, and the regular and sale price of a product. Save one row and that row saves, in place, no reload.
The counter counts what Google sees. A title template such as %title% %sep% %sitename% is 24 characters in a plain counter and 61 on the search result. This one resolves the variables first, so the number under the field is the number that decides whether you get truncated.
Search and replace answers before it acts. Tick the fields, type the phrase, and the row tells you how many matches it found and where, Elementor data included. Then you commit.
Prices, variable products included. An empty field is left alone, never read as clear. One price is written to every variation.
Turn one page into fifty. List a word and its replacements, one page per line, and get fifty drafts with the terms, the featured image and the Elementor data intact. A product line with twelve near identical descriptions stops being twelve editing sessions.
Delete with a redirect, in one step. The row goes to the trash and its old address is redirected where you choose.
Headings, without touching layout. H1 to H6 of a page, read from the body and from Elementor widgets, editable as text. Adding and removing is deliberately impossible: where a heading belongs is a decision for the editor, not a list.
Sorted by clicks. With Search Console connected, the grid orders itself by real impressions and clicks over a range you pick.
Seo Auto Link: one keyword, every page
Register a phrase on a page and the engine links it everywhere that phrase appears. From an index, not a search of your content on every request: the heaviest page on the test site resolves in 7.3 milliseconds.
It starts in shadow mode. The index builds while nothing is injected. You read the reports, you fix the conflicts, and only then do you switch it live.
Persian folding before matching. Arabic and Persian characters folded together, the zero width non joiner treated as a space, digits normalised. Your content is read through an offset map, never rewritten.
Rules that stop it embarrassing you. Longest phrase first, ranges locked so two keywords cannot overlap, word boundaries on both sides, no link from a page to itself, and never inside a heading, a button, an existing link, a shortcode or an attribute. Caps per page, per target and per paragraph, all off by default because the right number is your content’s, not a figure from a blog post.
It finds the links you wrote by hand years ago. A hand written link blocks the engine, so those phrases sit outside every report and never update when a destination moves. The pattern finder lists them and converts them in bulk, with the original of every page backed up first.
Nothing is lost when you leave. Deactivate the plugin and every link is written permanently into your content before it goes. Reactivate and the content returns to its clean state, byte for byte. Measured on a real site: 830 links across 227 pages, and the restored content identical to the original.
Search Console: what Google knows, on your screen
Upload your own Google service account key. The plugin reads your property and nothing leaves your site except the query to Google.
The gap, page by page. Google is already showing this page for these searches. Green means the phrase is on the page, word for word. Yellow means some of its words are. Red means the page does not say it at all, and red is where the opportunity is.
Index status, in Google’s own words. One URL at a time, grouped the way Search Console groups them: indexed, crawled but not indexed, discovered, excluded by a tag, blocked by robots.
Writing, with the site holding the decisions. The site decides which page, which phrase and where the sentence goes; the model only writes prose. A rewrite, not a paragraph bolted onto the end. Off by default, and it stays off until you configure an endpoint.
Two ways of not fooling yourself. A control group is drawn from every queue as a holdout, and every edit is dated so the 28 days before it can be compared with the 28 days after. If the whole site drops past a threshold you set, everything stops.
Link Nurse: broken links found and repaired
Content, excerpts, term descriptions, Elementor data and your XML sitemap. Relative links resolved against the page they sit on, which is where most scanners quietly lose a quarter of a site’s links.
Conservative on purpose. A 401, 403, 404 or 429 is checked again with a browser user agent before it is reported, because large publishers answer robots differently from browsers. Your own uploads are checked on disk, not over HTTP, which removes hundreds of self requests per scan.
A redirect chain is followed to its end. Up to ten hops, and a 301 that lands on a 404 is reported as broken with both codes, not as healthy.
Repairs keep your house style. A broken link is unwrapped and its text kept. Before the first repair to any field, the original is copied aside, so undo is per field and always available.
Internal Analytics: your visitors, your server
No third party anywhere in the path. One cookie holding a random session id, set in the browser, never sent to anyone.
Engagement, not page loads. Seconds accrue only while the tab is visible and the visitor actually moved, scrolled, typed or clicked.
Events out of the box. Outbound clicks, file downloads, tel and mailto links, form start and submit, CTA clicks, copy events.
Screens that answer questions. Visits, unique visitors, page views, engagement and bounce, average time, live visitors, and the pages and sources behind each number. Raw rows kept for a year by default, daily totals for twice that.
Persian and Arabic, from the first line
The same phrase can carry an Arabic character where a Persian one belongs, a zero width non joiner instead of a space, or a Persian digit where Google reports a Latin one. Every tool that matches text literally treats those as different phrases. This one folds them together first, everywhere: the linking engine, search and replace, keyword coverage and the reports.
The screens themselves speak English, Persian or Arabic, and each person on the site picks their own. Choosing one does not change the language of the rest of the dashboard.
It works with your SEO plugin, not against it
This does not replace Rank Math and does not try to. Rank Math owns the SEO title, the meta description and the redirect table; this plugin reads and writes those fields rather than inventing its own, and resolves redirects from that table instead of making an HTTP request. Yoast, SEOPress and All in One SEO are detected for the sitemap tools.
Tested on a live shop, not a clean install
Every release runs against a live Persian WooCommerce site with several thousand posts before it is packaged. That is where the findings come from: a Jalali date reaching a SQL comparison and returning zero rows on a site with 66,000 recorded visits; a scanner that had never reported a quarter of a site’s links because they did not begin with http; a bulk editor whose first version read an empty price field as clear. Each one is in the changelog with what caused it.
What it writes to your database
One table for the link index and eight for analytics, all prefixed. Keywords, exclusions and caps live in post and term meta. Settings live in options. Nothing is written outside your own database, and an uninstall switch decides whether all of it is removed or kept for a reinstall.
External services
Google Search Console API, used only when you upload your own service account key. Your site sends the property URL, date ranges and page addresses to Google in order to read back the searches and index states Google holds for you. Terms, privacy.
An AI endpoint of your choosing, optional and inert until you fill in a base URL, key and model. When configured, the text of the page being improved and the target phrases are sent to that endpoint so it can return prose. The provider is yours, so its terms are the ones that apply.
The sites you link to, when you scan for broken links. Each external address in your content is requested once, with a user agent naming this plugin and your site so the receiving site can see who is asking.
Author
Built in Tehran, and run every day on the two production sites it was written for. Bug reports and feature requests are welcome on the support forum; the author’s page has the longer story.

延伸相關外掛

文章
Filter
Mastodon