Add setting to disable Optimole URL rewriting for social meta tags (og:image / twitter:image)
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
调研方向
Start by locating the settings registration and the front-end HTML parser or URL replacement logic in the Optimole WordPress plugin. Trace how it handles og:image, og:image:secure_url, and twitter:image, then identify the existing settings and tests for exclusions. Done means a dashboard toggle preserves the original URLs when enabled and compatibility is checked with the listed SEO plugins.
由索引模型根据 Issue 内容生成。
描述
Impact: 75 · Confidence: 95 · Complexity: 40
Description
Problem
Optimole automatically rewrites image URLs inside page head social meta tags (og:image, og:image:secure_url, twitter:image) to Optimole CDN URLs. This can cause social media crawlers (such as Facebook Sharing Debugger, X/Twitter, LinkedIn) to fail to render link preview cards properly. Currently, site owners must add custom PHP filter code (optml_url_post_process) or manually exclude individual image filenames via Exclusions settings to prevent meta tag rewriting.
Desired Behavior
Provide an option in the Optimole WordPress plugin settings (e.g. under Advanced > Exclusions or General settings) to prevent Optimole from rewriting URLs inside social meta tags (og:image and twitter:image) across the site.
Acceptance Criteria
- Add a toggle setting in the WordPress plugin dashboard under Settings (e.g. "Disable URL replacement in social meta tags").
- When enabled, Optimole's front-end HTML parser/replacement logic bypasses
<meta>tags withproperty="og:image",property="og:image:secure_url", andname="twitter:image", leaving original media URLs intact. - Verify compatibility with popular SEO plugins (Rank Math, Yoast SEO, All in One SEO, SEOPress).
Customer Context
The customer (Douglas, a pro user running a content website) experienced broken Facebook link previews for articles because Optimole rewrote og:image tags to Optimole CDN URLs. The only available workaround in the plugin UI was adding per-image filename exclusions, which is unmaintainable for new articles. The customer requested a dashboard setting or global rule to stop Optimole from rewriting social meta tags in the page head.
Root Cause Analysis
The customer's underlying problem is that social network crawlers (Facebook, Twitter/X, etc.) require standard, un-processed image URLs in Open Graph (og:image) and Twitter Card (twitter:image) HTML meta tags. Optimole's HTML post-processing parser automatically rewrites all image URLs on the page—including those inside head meta tags—to CDN URLs. When social platforms scrape the page, CDN URL parameters or format negotiations can prevent link previews from generating correctly. The plugin currently lacks a user-configurable setting or exclusion rule to preserve original URLs specifically within head meta tags site-wide, forcing users to rely on manual PHP snippets (optml_url_post_process) or tedious per-file exclusions.
Reasoning
The customer is reporting that Optimole automatically rewrites image URLs in Open Graph and Twitter Card social meta tags (, ) to Optimole CDN URLs. When social crawlers (like Facebook) fetch these rewritten URLs, previews can fail or display incorrectly. Currently, there is no setting in the Optimole WordPress plugin dashboard or cloud interface to disable social meta tag URL rewriting. The support agent confirmed this gap ("there isn't a dashboard setting yet to stop Optimole rewriting og:image/twitter:image") and provided a PHP snippet filter workaround. Exclude rules currently require per-image exclusions by filename, which is not scalable for site owners publishing new content continuously. While the customer initially asked if AVIF was forced, the core problem is the lack of a site-wide toggle or rule in Optimole settings to disable social meta tag rewriting. Root cause analysis confirms this is a genuine missing product feature/toggle in the Optimole WordPress plugin (Codeinwp/optimole-wp).
Source: HelpScout #3478424614
Generated by feature-request-triage workflow (ID: feature-request-triage_6acac3cfcf3413.17158397)
- 主要语言
- PHP
- 星标
- 74
- 派生
- 14
- 平均合并
- 2 天 9 小时
- 30 天内合并 PR
- 22
环境准备
- 提供 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
Codeinwp/optimole-wp 的其他 Issue
-
Image URL replacement passes an integer cache token to the Optimole SDK可能已有人在做 @selul 于 7 天前认领。 未关闭bug bug-report bug-report-triage crash-report
难度 3/5 1-2 天 新手友好度 55/100
Codeinwp/optimole-wp#1187 · 2 条评论 · 已指派 1 人 ·
维护者通常 1 天内回复
-
Image parser uses a data: placeholder from data-src as the image URL, so the real src misses srcset enhancement可能已有人在做 @selul 于 7 天前认领。 未关闭bug bug-report
难度 4/5 1-2 天 新手友好度 56/100
Codeinwp/optimole-wp#1186 · 2 条评论 · 已指派 1 人 ·
维护者通常 1 天内回复
-
customer report feature-request-triage
难度 5/5 一周以上 新手友好度 35/100
Codeinwp/optimole-wp#1179 ·
维护者通常 1 天内回复
-
bug bug-report bug-report-triage crash-report
难度 4/5 3-5 天 新手友好度 45/100
Codeinwp/optimole-wp#1163 · 4 条评论 ·
维护者通常 1 天内回复
-
customer report feature-request-triage
难度 3/5 1-2 天 新手友好度 55/100
Codeinwp/optimole-wp#1151 ·
维护者通常 1 天内回复
查看 Codeinwp/optimole-wp 的全部 Issue
相似的 Issue
-
bug P2
难度 2/5 1-3 小时 新手友好度 84/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 82/100
Automattic/blocks-engine#3618 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 62/100
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 70/100
MagnaCapax/PMSS#1206 ·
维护者通常 3 天内回复
-
`render_block_query` overwrites the `core/query` namespace, breaking context for enhanced pagination未关闭
难度 2/5 1-3 小时 新手友好度 82/100
humanmade/query-filter#72 ·