-
Hello, friend.
First of all, I am Korean, so I will speak through a translator.
Please understand if it’s not accurate.I’m building a site through Cloudways, and I’m using RankMath.
I registered the site map through the Google search console.1. 11/17 First time I registered, I got an error saying “I can read the site map but there is an error that I know”, and I tried many things while consulting the Cloudways team.
2. I checked on 11/19 and found that it was registered on the Google search console normally.
But still
[https://wp-yeo.com/sitemap_index.xml]
If you go into the link, you’ll see a blank white screen.What’s the problem?
-
Hello,
Thank you for contacting us and sorry for any inconvenience that might have been caused due to that.
This issue is occurring because on your database entries, there are some Unicode characters that are preventing the sitemap from correctly loading.
Please access your WordPress database and check the table
wp_options. You’ll notice entries likeblognamewith Unicode characters instead of the correct characters in there.To be more specific, you may take a look if you find a similar entry like
위치 사이트맵in theoption_valuecolumn. Here is an example below for your reference:By fixing those entries, the sitemap should start working fine.
Let us know how it goes. Looking forward to helping you.
Thank you.
Hello,
We might need to take a closer look at the settings. Please edit the first post on this ticket and include your WordPress & FTP logins in the designated Sensitive Data section.
Please do take a complete backup of your website before sharing the information with us.
It is completely secure and only our support staff has access to that section. If you want, you can use the below plugin to generate a temporary login URL to your website and share that with us instead:
https://wordpress.org/plugins/temporary-login-without-password/
You can use the above plugin in conjunction with the WP Security Audit Log to monitor what changes our staff might make on your website (if any):
https://wordpress.org/plugins/wp-security-audit-log/
Looking forward to helping you.
Thank you.
Hello,
Thank you for sharing the details from your Google Search Console regarding the indexing issues on your website.
Based on the information you provided, it looks like there are a few different reasons why certain pages on your site are not being indexed.
The ‘NOINDEX’ tag instructs search engines not to index a page. If this page is intentionally set to ‘NOINDEX’, then it’s working as expected.
Excluded by tag ‘NOINDEX’ (https://wp-yeo.com/author/yeoword/):
A 404 error means the page doesn’t exist. You need to check if this URL is correct and if the page should exist.
Not Found (404) (https://wp-yeo.com/테스트글입니다/):
However we checked your posts lists and we found the post
테스트글 입니다exists but the slug for that post is not테스트글입니다rather the slug is테스트글-입니다.If you look closely you will see that there is a
-in betweenWe suggest you to create a 301 redirect from
https://wp-yeo.com/테스트글입니다/tohttps://wp-yeo.com/테스트글-입니다/For the pages listed (various categories and a sample page), you should evaluate whether these pages provide unique and valuable content that should be indexed.
If they are essential for users, ensure there are no conflicting tags like canonical or noindex, and the content is unique and useful.
Crawled – No current index is generated status can occur for a variety of reasons, including a page being recently changed, the presence of a canonical tag pointing to another URL, or Google deciding not to index the page currently (which could be due to quality or duplicate content issues).
We hope that helps, and please don’t hesitate to get in touch if you have any other questions.
Thank you.
The ticket ‘sitemap / google search console /’ is closed to new replies.