Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

No Index tag on SEO Components #1858

Closed
monzuralam opened this issue Mar 23, 2024 · 7 comments
Closed

No Index tag on SEO Components #1858

monzuralam opened this issue Mar 23, 2024 · 7 comments

Comments

@monzuralam
Copy link

monzuralam commented Mar 23, 2024

Recently, I used faustjs on my headless WordPress Project. my development ongoing. So, I want to discourage search engines on my website.

In SEO, Compoenets there are no features about it.

File Location: components/SEO/SEO.js

By default index behavior is true, if anyone wishes to noindex then just pass props false;

@theodesp
Copy link
Member

Hey @monzuralam. Is there a particular issue you are facing here? Thanks

@monzuralam
Copy link
Author

Hey @theodesp, I can fix it on my current project by modifying the SEO Component. But I think it should be updated globally.
In WordPress, we can add an index & no index tag on any page/post. Faustjs is a WordPress Headless framework, We should update it on the SEO component & smoothly manage the index & no index tag.

Currently, in this framework, we can't manage it.

@theodesp
Copy link
Member

Hey @monzuralam . Thanks for the report. Would you be able to submit a PR about it?

@mindctrl
Copy link
Member

Ideally noindex would be tied to the "Discourage search engines from indexing this site" setting under Settings > Reading in wp-admin. It looks like WPGraphQL does not expose this setting under readingSettings. I think we need to open an issue/PR upstream before we can support it here.

@theodesp
Copy link
Member

cc @jasonbahl

@jasonbahl
Copy link
Contributor

I'd recommend using register_graphql_field in the meantime to add settings like this to the schema.

@theodesp
Copy link
Member

Hey @monzuralam thank you for the question. We are going to move this ticket into the discussions section and you can review @jasonbahl suggestion as well.

@wpengine wpengine locked and limited conversation to collaborators May 29, 2024
@theodesp theodesp converted this issue into discussion #1893 May 29, 2024

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Projects
None yet
Development

No branches or pull requests

5 participants