Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Noindex issue with new google search console #435

Open
alanski66 opened this issue Oct 2, 2022 · 4 comments
Open

Noindex issue with new google search console #435

alanski66 opened this issue Oct 2, 2022 · 4 comments

Comments

@alanski66
Copy link

Description

I recently started a new marketing site and started to add the domain to google search consle as opposed to url. The domain is a new thing google offer as opposed to just adding url so I went that route.
After two weeks of submitting SEO sitemaps I kept getting noindex flags from google.
I checked the raw page output and headers sent - noindex issue persisted, along with a very confusing HTTPS message

Total head scratch.

Having lost time on SEO juice building i just swapped out this SEO plugin to another commercial plugin i have used on other sites. Submitted site map - and we are back in the index. Go figure.

Not sure whats going on here but it ain't good.

Steps to reproduce

  1. Just use it as intended and set environment correctly
  2. Request search index via google console via submission of SEO produced sitemaps

Additional info

  • Craft version: 4
  • SEO version: latest
  • PHP version: 8.1
  • Database driver & version: mySQL5.7
@remcoov
Copy link

remcoov commented Oct 4, 2022

Yes, this is the same as #432

@SoftboiledStudios
Copy link

I'm still experiencing this issue?

@mateostabio
Copy link

If anyone else is experiencing this, it's because the plugin is still looking for ENVIRONMENT variable. Craft CMS 4 now uses CRAFT_ENVIRONMENT. So a hack around this problem until this plugin is updated is to have both variables in your .env file.

CRAFT_ENVIRONMENT=production
ENVIRONMENT=production

@niektenhoopen
Copy link
Contributor

The work-around should not be necessary anymore in the latest version of the plug-in.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants