Support » Plugin: Yoast SEO » japanese keyword attack on search console

  • Resolved Srabani Roy

    (@srabaniroy1994)


    When I check in Google search bar for my website appear in the google’s results. I have always the english version of the site with meta description in English but while I’m using the japanese version of google and my computer is set up in japanese.
    How can I fix this ?

    • This topic was modified 4 weeks, 1 day ago by Srabani Roy.

    The page I need help with: [log in to see the link]

Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Support Priscilla Chapman

    (@priscillamc)

    Hi @srabaniroy1994,

    Just to clarify, your page titles and meta descriptions are written in English, but you see Japanese in the search result titles and descriptions. Is that correct?

    We did not find any Japanese text in any of the meta tags generated by Yoast SEO, so the plugin doesn’t appear to cause this problem.

    If search results aren’t appearing as expected for certain pages, we recommend using the Request Indexing tool in the Google Search Console. We have more details in this guide: How to update information in Google search results.

    If this happens for many pages, you may need to re-submit your sitemap. Please be aware that it can take a few days or more for Google to crawl your site and update the search results.

    Srabani Roy

    (@srabaniroy1994)

    okkk.. thank you mam

    Plugin Support Michael Tina

    (@mikes41720)

    Hi,

    We’re glad to be of assistance. Setting this to resolved.

    Srabani Roy

    (@srabaniroy1994)

    sorry sir … it’s not resolved .. i have to find new problem in my plugins…
    This page contains the following errors:
    error on line 5 at column 6: XML declaration allowed only at the start of the document
    Below is a rendering of the page up to the first error.

    Plugin Support Michael Tina

    (@mikes41720)

    Hello,

    Thanks for your response.

    This issue typically happens when a plugin or theme function incorrectly adds empty whitespace at the beginning of the sitemap. Please view the source code of your sitemap.

    You can learn more about how to troubleshoot it in this article here — https://yoast.com/help/xml-sitemap-error/

    Srabani Roy

    (@srabaniroy1994)

    hiii sir …
    thanks for your suggestion.
    but i can’t see my sitemap.
    http://www.technsol.org/sitemap_index.xml
    This page contains the following errors:
    error on line 5 at column 6: XML declaration allowed only at the start of the document
    Below is a rendering of the page up to the first error.

    Plugin Support Carl B

    (@devnihil)

    We checked on your site’s sitemap at http://www.technsol.org/sitemap_index.xmland do see the page is generating an error of ‘XML declaration allowed only at the start of the document.‘ We reviewed the source code of the page and found that the document does contain a whitespace for the first line of the file, which is what is causing the issue (see image here).

    The error ‘XML declaration allowed only at the start of the document‘ is caused when another file, plugin, or theme adds white space to the beginning of the sitemap file. You will need to view the source code of the sitemap_index.xml document in order to confirm this, and we have additional information on this and how to resolve this error at the following link: https://kb.yoast.com/kb/xml-sitemap-error/.

    The additional white space in the sitemap file can be caused by an empty line at the end of your theme’s functions.php file, or by having a blank line or space at the beginning of your wp-config.php file.

    In order to resolve this, we would first recommend clearing your site’s caching. If you are not sure how to clear your server caching, please speak with your host provider. Does clearing your caching from your caching plugin (W3TC, WP Supercache, etc), server (Varnish, LiteSpeed, or others), or CDN (such as Cloudflare, Amazon AWS, etc) resolve the issue? If after clearing your site’s cache you are still experiencing the error on the sitemap, we would then next recommend checking your theme’s functions.php file for an empty line at the end of the file, as well as your wp-config.php file for any additional spaces at the beginning of the file.

    If you cannot find any empty lines at the end of your theme’s functions.php file or blank lines or spaces at the start of the wp-config.php, we would next recommend running a conflict check to identify whether another plugin or them is outputting the additional white space in the sitemap file. The fastest way to do this is to deactivate all non-Yoast plugins and switch to a standard theme like TwentyNineteen.

    Test this on your development or staging site, if you have one. If not, we recommend using the Health Check & Troubleshooting plugin. This plugin allows you to run a conflict check without affecting normal visitors to your site. If you are unfamiliar with checking for conflicts, you can find a step-by-step guide that will walk you through the process here: https://kb.yoast.com/kb/how-to-check-for-plugin-conflicts/

Viewing 7 replies - 1 through 7 (of 7 total)
  • You must be logged in to reply to this topic.