Codeinwp / Codeinwp/optimole-wp

Exclude Optimole URLs from Schema Images

Open
#854 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

medium new feature
Dominant language
PHP
Stars
72
Forks
14
Avg merge
2d 9h
Merged PRs (30d)
15

Description

What problem does this address?

Images referenced inside of schema markup (for example, rich product snippets) typically send the Optimole image URL to the search engines, not the clean, local URL.

For example:
https://mlyqxds8ijge.i.optimole.com/w:2048/h:1152/q:80/f:best/https://some-site.com/wp-content/uploads/image.jpg

Instead of:
https://some-site.com/wp-content/uploads/image.jpg

What is your proposed solution?

It would be ideal if Optimole could optionally exclude the images referenced inside of the schema markup so they get a normal URL and not the Optimole URL. Basically, I think we want the option to excluded images inside of script tags, or script tags with an ID or class:

<script id="website-schema" type="application/ld+json">...schema content...</script>
Will this feature require documentation? (Optional)

None

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or entry points are named. Start by tracing where Optimole rewrites image URLs and how schema markup in script tags is handled. Done means an optional exclusion prevents Optimole URLs from appearing in schema images while leaving other image optimization behavior unchanged.

Written by the indexing model from the issue text.

Assessment

Tech stack
php
Domain
web-dev
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.