SEOmatic facilitates modern SEO best practices & implementation for Craft CMS 3. It is a turnkey SEO system that is comprehensive, powerful, and flexible.
The reason we suspect that the above line is causing us this issue is because we are running craft headless and our baseCpUrl matches the GraphQL in the first segment IE
baseCpUrl: https://mycraft.com.au/GraphQL: https://mycraft.com.au/api
Currently we are getting this response back from our Craft instance in Production for all our pages even when we have set Robots to all:![image](https://github.com/nystudio107/craft-seomatic/assets/21113405/670eb0b1-bc96-496e-8012-14fcaac8cdc3)
And we suspect that it was introduced with the following commit: https://github.com/nystudio107/craft-seomatic/commit/c34b6d0b585abde52efaeac5e8ec7045c8f5772b![image](https://github.com/nystudio107/craft-seomatic/assets/21113405/db30d97e-8ad7-404a-8a93-560092657a65)
The reason we suspect that the above line is causing us this issue is because we are running craft headless and our baseCpUrl matches the GraphQL in the first segment IE baseCpUrl: https://mycraft.com.au/ GraphQL: https://mycraft.com.au/api
If we look at the implementation of getIsCpRequest in https://github.com/craftcms/cms/blob/main/src/web/Request.php#L610![image](https://github.com/nystudio107/craft-seomatic/assets/21113405/10230973-a291-401b-9ad3-1b9d20c0e7bb)
We can see it is determined by checking if the first segment matches the cpTrigger setting, which in our case is null which leads us to the following section on https://craftcms.com/docs/4.x/config/general.html#basecpurl![image](https://github.com/nystudio107/craft-seomatic/assets/21113405/af831ba1-620f-44ae-9b38-314ae185771a)
This means cpTrigger is being set to baseCpURL, which in result is returning
for all our pages.
Could this be looked into please as our website has disappeared from Google and this may be the reason?
Note: We have fixed our problem for the meantime by rolling back to 4.0.37