• Resolved jclarkeuk

    (@jclarkeuk)


    What used to take no longer than 60 seconds to do, Google now seem to make this as difficult as possible.

    I cannt for the life of me get my site to verify in either Site Kit (installed plugin to site) or Google Search Console. I have no idea why?

    I have cleaned up the cache using WP Super Cache, renamed the htaccess, nothing works!

    Help… cheers.. John

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

Viewing 13 replies - 16 through 28 (of 28 total)
  • Thread Starter jclarkeuk

    (@jclarkeuk)

    So… I changed theme & tried again.. no luck, I deactived all my plugins… no luck.. I am also thinking now that its a DNS hosting company issue??

    Thread Starter jclarkeuk

    (@jclarkeuk)

    I have https://www.capti.co.uk on the same host & its fine…

    Alright can you please check is there any errors in the browser’s console on the same screen where you are stuck.

    We’ll need to remove the existing site_id from the Site Kit service side. Probably you’ll be able to setup Site Kit again. On this we’ll follow later this week or coming Monday.

    Thanks for bearing with me.

    Best Regards,

    Thread Starter jclarkeuk

    (@jclarkeuk)

    Hi, I hope you had a good weekend. So, I have disabled all the plugins & changed theme & deleted the cache, still nothing… the error console shows

    Content Security Policy: Ignoring "'unsafe-inline'" within script-src or style-src: nonce-source or hash-source specified 5
    Content Security Policy: Ignoring ‘x-frame-options’ because of ‘frame-ancestors’ directive.
    Content Security Policy: Ignoring "'unsafe-inline'" within script-src or style-src: nonce-source or hash-source specified 2
    Some cookies are misusing the recommended “SameSite“ attribute 2
    Content Security Policy: Ignoring "'unsafe-inline'" within script-src or style-src: nonce-source or hash-source specified
    Content Security Policy: Ignoring "'unsafe-inline'" within script-src or style-src: nonce-source or hash-source specified 2
    Content Security Policy: Ignoring "'unsafe-inline'" within script-src or style-src: nonce-source or hash-source specified
    Thread Starter jclarkeuk

    (@jclarkeuk)

    I have run the google data test tool & it seems that google cannot access the robots.txt file… it is clearly there you can see it /robots.txt but google cannot see it???

    The URL is unreachable. Ensure robots.txt is accessible and the server is responding with a 200 status code.

    @jclarkeuk ,

    I can’t access your site. Is it down for now?

    Let us know when its up so we can inspect your site for you.

    Thread Starter jclarkeuk

    (@jclarkeuk)

    Actually I changed the namesevers then verified it through 123reg with a DNS TXT entry… its verified now but it was a bit of a cheat. I am now having troubling indexing through google as it cant find the robots.txt or sitemap so I have changed the nameservers back and will look again tomorrow.

    Cheers A

    Thanks for the update.

    Feel free to respond back when your website is back in case if you are still encountering the issue.

    Best Regards,

    Thread Starter jclarkeuk

    (@jclarkeuk)

    So here is an update – by the way the site is fine… its resolving no ttrouble.

    I have managed to get verified in google by adding DNS to 123reg, now I am having trouble with google not finding my site, it wont fetch the sitemap! I have validated it and its fine, its just google being google. It also wont index the site, when I try a live url test it comes back with URL is unknown to Google. as for the sitemap I am getting Sitemap could not be read
    General HTTP error. Bing and every other search engine I have submitted to are fine!

    Thread Starter jclarkeuk

    (@jclarkeuk)

    Do you think it might be an htaccess issue?? I will post this here for you to look at, I have looked and cannot see anything obvious ie nofollow.

    Thread Starter jclarkeuk

    (@jclarkeuk)

    # BEGIN rlrssslReallySimpleSSL rsssl_version[4.0.15]
    <IfModule mod_rewrite.c>
    RewriteEngine on
    RewriteCond %{HTTPS} !=on [NC]
    RewriteCond %{REQUEST_URI} !^/\.well-known/acme-challenge/
    RewriteRule ^(.*)$ https://%{HTTP_HOST}/$1 [R=301,L]
    </IfModule>
    # END rlrssslReallySimpleSSL
    # BEGIN WordPress
    # The directives (lines) between “BEGIN WordPress” and “END WordPress” are
    # dynamically generated, and should only be modified via WordPress filters.
    # Any changes to the directives between these markers will be overwritten.
    <IfModule mod_rewrite.c>
    RewriteEngine On
    RewriteRule .* – [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]
    RewriteBase /
    RewriteRule ^index\.php$ – [L]
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule . /index.php [L]
    </IfModule>

    # END WordPress
    # php — BEGIN cPanel-generated handler, do not edit
    # Set the “ea-php74” package as the default “PHP” programming language.
    <IfModule mime_module>
    AddHandler application/x-httpd-ea-php74 .php .php7 .phtml
    </IfModule>
    # php — END cPanel-generated handler, do not edit
    # BEGIN HttpHeaders
    # The directives (lines) between “BEGIN HttpHeaders” and “END HttpHeaders” are
    # dynamically generated, and should only be modified via WordPress filters.
    # Any changes to the directives between these markers will be overwritten.
    # END HttpHeaders
    # BEGIN HttpHeadersAuth
    # The directives (lines) between “BEGIN HttpHeadersAuth” and “END HttpHeadersAuth” are
    # dynamically generated, and should only be modified via WordPress filters.
    # Any changes to the directives between these markers will be overwritten.
    # END HttpHeadersAuth
    # BEGIN HttpHeadersCompression
    # The directives (lines) between “BEGIN HttpHeadersCompression” and “END HttpHeadersCompression” are
    # dynamically generated, and should only be modified via WordPress filters.
    # Any changes to the directives between these markers will be overwritten.
    # END HttpHeadersCompression
    # BEGIN HttpHeadersContentType
    # The directives (lines) between “BEGIN HttpHeadersContentType” and “END HttpHeadersContentType” are
    # dynamically generated, and should only be modified via WordPress filters.
    # Any changes to the directives between these markers will be overwritten.
    # END HttpHeadersContentType
    # BEGIN HttpHeadersExpires
    # The directives (lines) between “BEGIN HttpHeadersExpires” and “END HttpHeadersExpires” are
    # dynamically generated, and should only be modified via WordPress filters.
    # Any changes to the directives between these markers will be overwritten.
    # END HttpHeadersExpires
    # BEGIN HttpHeadersTiming
    # The directives (lines) between “BEGIN HttpHeadersTiming” and “END HttpHeadersTiming” are
    # dynamically generated, and should only be modified via WordPress filters.
    # Any changes to the directives between these markers will be overwritten.
    # END HttpHeadersTiming
    # BEGIN HttpHeadersCookieSecurity
    # The directives (lines) between “BEGIN HttpHeadersCookieSecurity” and “END HttpHeadersCookieSecurity” are
    # dynamically generated, and should only be modified via WordPress filters.
    # Any changes to the directives between these markers will be overwritten.
    # END HttpHeadersCookieSecurity

    Thread Starter jclarkeuk

    (@jclarkeuk)

    I deleted the http header plugin a while ago so have now just removed from start to end of http headers in htaccess… still no luck with index or sitemap.

    Glad to hear finally you are abled to setup Site Kit. For Sitemap & index related issue I’d recommend you to contact product experts at Search Console forum as they’d have more insights on it.

    Happy Weekend!

Viewing 13 replies - 16 through 28 (of 28 total)
  • The topic ‘The necessary verification token could not be found on your site’ is closed to new replies.