<p>Turns out the issue was being caused by the fact that <strong>another SEO plugin was still installed</strong>.</p>
<p>Client was using the <code>ether/seo</code> plugin before, and I left it installed intentionally so the client could have some time to migrate values from that plugin's fields into SEOmatic entry overrides.</p>
<p>Now that the client has finished migrating values I've removed the the <code>ether/seo</code> plugin and its field type, and things appear to be working properly now with SEOmatic entry overrides actually overriding Content SEO values.</p>

CC BY-SA 4.0
2024-03-06T17:16:41.457Z
2024-03-06T17:16:41.457Z
Roger Glenn
<p>As a test, here's a blog entry title with it set up to use the <code>{{ entry.title }}</code> for the Content SEO settings for the Blog section:</p>
<p><a href="https://i.sstatic.net/l2rT7.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/l2rT7.png" alt="enter image description here" /></a></p>
<p>Then I set up a SEO Settings field and override the Title like so:</p>
<p><a href="https://i.sstatic.net/l9hle.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/l9hle.png" alt="enter image description here" /></a></p>
<p>...and then I reloaded the frontend, and it's displaying as expected with the new <code>Custom Title</code> text:</p>
<p><a href="https://i.sstatic.net/iRE7j.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/iRE7j.png" alt="enter image description here" /></a></p>
<p>Can you provide similar screenshots for your setup, so we can see what's different, and why this isn't working as expected for you?</p>

CC BY-SA 4.0
2024-03-05T01:33:06.277Z
Issue description updated with screenshots
Roger Glenn
CC BY-SA 4.0
2024-03-04T21:46:50.023Z
2024-03-04T21:46:50.023Z
andrew.welch
<pre><code>Craft CMS 4.8.0
SEOmatic 4.0.42
</code></pre>
<p>I have configured the meta cascade according to plugin documentation - defined Global and Section SEO settings with default values - and I've also created an SEO Settings field and attached it to my entries.</p>
<p><strong>Content SEO Settings:</strong>
<a href="https://i.sstatic.net/20kAf.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/20kAf.png" alt="enter image description here" /></a></p>
<p><strong>Entry SEO Settings:</strong>
<a href="https://i.sstatic.net/UO8Nd.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/UO8Nd.png" alt="enter image description here" /></a></p>
<p><strong>Output:</strong>
<a href="https://i.sstatic.net/lbgMg.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/lbgMg.png" alt="enter image description here" /></a></p>
<p>I'm finding that <strong>whatever overrides I define on an entry are NOT overriding Content SEO values.</strong> In this example the <code>&amp;amp;</code> was replaced with <code>and</code> in the SEO Title Source override field.</p>
<p>No SEOmatic tags have been added to my document head template, so the tags being rendered are automatically generated by the SEOmatic plugin.</p>
<p>Things I've tried:</p>
<ol>
<li>Cleared all caches,</li>
<li>Confirmed the document head template partial does not contain any Craft <code>{% cache %}</code> tags,</li>
<li>Resaved sections,</li>
<li>Resaved entries, and</li>
<li>Turned on debug bar and checked SEOmatic tab.</li>
</ol>
<p>The debug bar &gt; SEOmatic tab shows <code>no variables present</code> for Entry SEO overrides, even though the override toggles are turned on and custom values are entered into the entry's SEO Settings field, which confirms what I'm noticing in rendered pages.</p>
<p>Plugin documentation seems to indicate the Entry SEO overrides should automatically be picked up and override Content SEO values, but that's not happening.</p>
<p>Am I missing a step somewhere, or do I need to insert an SEOmatic tag into the document head to force the overrides?</p>

CC BY-SA 4.0
2024-03-04T21:36:10.703Z
Can you provide a screenshot of the SEO Settings field on one of your entries where this is not working as you're expecting it to?
andrew.welch
CC BY-SA 4.0
2024-03-06T03:19:16.437Z
Can you try re-saving your Content SEO settings? Also check to ensure you have things filled out in Global SEO as well? Worst case you can file an issue, and we can get on a video conf and have a look: https://github.com/nystudio107/craft-seomatic/issues
andrew.welch
CC BY-SA 4.0
2024-03-06T16:28:35.993Z
Global SEO is fully populated. Tried resaving Content SEO Settings and clearing caches, and still seeing the same behavior - entry overrides not overriding Content SEO Settings. I'll submit an issue in GitHub.
Roger Glenn
<plugin-seomatic><seomatic>
Entry SEO Settings values not overriding Content SEO Setting values
# Entry SEO Settings values not overriding Content SEO Setting values

(Asked by: username_0 on 2024-03-04)

Craft CMS 4.8.0
SEOmatic 4.0.42

I have configured the meta cascade according to plugin documentation - defined Global and Section SEO settings with default values - and I've also created an SEO Settings field and attached it to my entries.
Content SEO Settings:

Entry SEO Settings:

Output:

I'm finding that whatever overrides I define on an entry are NOT overriding Content SEO values. In this example the & was replaced with and in the SEO Title Source override field.
No SEOmatic tags have been added to my document head template, so the tags being rendered are automatically generated by the SEOmatic plugin.
Things I've tried:

Cleared all caches,
Confirmed the document head template partial does not contain any Craft {% cache %} tags,
Resaved sections,
Resaved entries, and
Turned on debug bar and checked SEOmatic tab.

The debug bar > SEOmatic tab shows no variables present for Entry SEO overrides, even though the override toggles are turned on and custom values are entered into the entry's SEO Settings field, which confirms what I'm noticing in rendered pages.
Plugin documentation seems to indicate the Entry SEO overrides should automatically be picked up and override Content SEO values, but that's not happening.
Am I missing a step somewhere, or do I need to insert an SEOmatic tag into the document head to force the overrides?

**Tags:** plugin-seomatic, seomatic

> **Comments:**
> **username_1**: Can you provide a screenshot of the SEO Settings field on one of your entries where this is not working as you're expecting it to?  
> **username_1**: Can you try re-saving your Content SEO settings? Also check to ensure you have things filled out in Global SEO as well? Worst case you can file an issue, and we can get on a video conf and have a look: https://github.com/nystudio107/craft-seomatic/issues  
> **username_0**: Global SEO is fully populated. Tried resaving Content SEO Settings and clearing caches, and still seeing the same behavior - entry overrides not overriding Content SEO Settings. I'll submit an issue in GitHub.  

---

## 2 answers

### Answer by username_0 on 2024-03-06. Score: 2

Turns out the issue was being caused by the fact that **another SEO plugin was still installed**.

Client was using the `ether/seo` plugin before, and I left it installed intentionally so the client could have some time to migrate values from that plugin's fields into SEOmatic entry overrides.

Now that the client has finished migrating values I've removed the the `ether/seo` plugin and its field type, and things appear to be working properly now with SEOmatic entry overrides actually overriding Content SEO values.


---

### Answer by username_1 on 2024-03-04. Score: 1

As a test, here's a blog entry title with it set up to use the `{{ entry.title }}` for the Content SEO settings for the Blog section:

[![enter image description here](https://i.sstatic.net/l2rT7.png)](https://i.sstatic.net/l2rT7.png)

Then I set up a SEO Settings field and override the Title like so:

[![enter image description here](https://i.sstatic.net/l9hle.png)](https://i.sstatic.net/l9hle.png)

...and then I reloaded the frontend, and it's displaying as expected with the new `Custom Title` text:

[![enter image description here](https://i.sstatic.net/iRE7j.png)](https://i.sstatic.net/iRE7j.png)

Can you provide similar screenshots for your setup, so we can see what's different, and why this isn't working as expected for you?

> **Comments:**
> **username_0**: Issue description updated with screenshots  

---

