內容簡介
Marcelo Site Connector 外掛簡化了將網站連接至 Google Search Console、Google Analytics 和 Google Tag Manager 的過程，無需手動插入程式碼。安裝後，外掛可自動處理這些標籤，提升網站的 SEO 效率。
【主要功能】
• 自動將 Google 標籤放入網站的 <head> 區域
• 儲存並顯示頁面的 meta 描述
• 儲存並管理頁面在搜尋結果中的標題
• 儲存 LocalBusiness schema 區塊
• 管理不存在的地址重定向
• 讀取和寫入 Elementor 建置的頁面佈局
外掛標籤
開發者團隊
原文外掛簡介
Connecting a website to Google Search Console, Google Analytics or Google Tag Manager always ends the same way: a line of code has to go into the site’s
.WordPress can be given permission to write posts, pages and media over its own REST API, but not to write there. So the last step of connecting any of those three is a person being asked to paste a snippet into a theme file or into an SEO plugin’s settings — and the person being asked is usually a business owner who paid somebody to build the site two years ago.
This plugin removes that step. Install it once, and Marcelo can place those tags itself.
What it does
Places up to three Google tags in the site’s
— a Search Console verification, an Analytics tag and a Tag Manager container — built from the identifier of each rather than from any markup it was handed.Stores a description for a page that has none, and prints it as that page’s meta description — the sentence a search engine shows under the page in its results. WordPress core keeps no such field, and every SEO plugin uses its own hidden one, so a description written into any of those keys is invisible on a site running a different plugin.
Stores the title a page should go by in search results and in a browser tab, and hands it to WordPress through pre_get_document_title — the filter core publishes for exactly this, and the one every common SEO plugin uses. This is not the post’s own title: post_title is the name of the page in the admin and usually the heading a visitor reads, and changing it does not change the title a search engine shows on a site running any SEO plugin.
Stores a LocalBusiness schema block describing the business, as JSON-LD in the head of every page.
Stores redirects for addresses that no longer exist, and sends visitors on to the page that replaced them.
Reads and writes the layout of a page built with Elementor, so the text of such a page can be edited at all. WordPress keeps a page’s text in post_content; Elementor keeps its own copy in a protected postmeta field and prints that instead, so a write to post_content on an Elementor page succeeds and changes nothing a visitor reads.
Puts a tap-to-call bar in front of visitors: one fixed element carrying the business’s phone number as a tel: link, printed at wp_footer on every page. It is Marcelo’s own element and touches nothing the site already had, so clearing it removes it completely.
Reports how this site serves robots.txt, and — only where WordPress generates it — lets a named crawler back in that robots.txt was turning away. A robots.txt file sitting in the site’s root is refused rather than touched: the webserver serves that file directly and WordPress is never asked for one, so nothing a plugin does could change what a crawler reads.
Points a page’s canonical link back at the page itself, where the one on it names another website. This is the only thing here that displaces markup the site was already printing rather than adding markup of its own — see below for exactly how far that reaches, and where it stops.
Adds a translated page’s own link among its hreflang alternates where it is missing one — the one entry that says “this page is itself”. Nothing else in the head is touched: whatever else prints the page’s other alternates is left exactly as it is, and only the language code is stored — the address is always built from the page’s current request, never stored, so it stays correct if the domain ever changes.
Saves an oversized picture in the site’s own media library again at a smaller size, keeping the untouched original beside it so it can be put back. This is the only thing here that overwrites a file rather than a value in the database, and it is bounded accordingly: only an attachment this site really owns, only a file inside its own uploads directory, only when the file still weighs what the caller says it weighed, never a GIF or an SVG, and never at all on a host with no image library. A re-encode that came out larger is undone in full.
Draws a page that does not exist yet in this site’s own theme — header, navigation, styling and footer — from a title and some text, and hands the finished page back without storing any of it. Nothing is created: no post, no draft, no revision, no row of any kind. The page is assembled in memory for the length of one request, and the database is held read-only underneath it, so anything on the site that would ordinarily write while a page renders is refused rather than trusted.
Exposes all of it over the REST API to users who can already manage_options.
What it does not do
It does not phone home. No connection is ever made from this plugin to any server, including ours. Everything travels the other way, over your site’s own authenticated REST API.
It contains no tracking, analytics or telemetry of its own.
It stores no markup at all. Three identifiers are kept — a verification token, a G- measurement id, a GTM- container id — and nothing else. Google’s scripts are then loaded through wp_enqueue_script, from a URL this plugin builds, so no text a caller sends can reach a visitor’s browser: there is no path by which any is stored.
The schema field is held to a far narrower rule than the rest: exactly one