CharlieHamu

I only get the “Your site may not be ready for Site Kit” message, at the top of the plugins page, when I activate Site Kit. I can’t activate site kit when in troubleshooting mode, only enable it. When I enable it (either by first enabling troubleshooting mode as you suggest and then enabling Site Kit within troubleshooting mode, or by directly clicking “troubleshoot” next to Site Kit), I still get the same results on the Site Kit dashboard: “Data error in Search Console” / “You are probably offline.”

Another possible clue. I deactivated Site Kit and activated JetPack. Inside JetPack, when I went to turn on stats, I got the response “Error updating settings. FetchNetworkError”. I’ve now deactivated JetPack.

• This reply was modified 3 years, 2 months ago by CharlieHamu.

I’m confused. HTTP is set to redirect to HTTPS in my hosting setup, and does so. Try visiting https://DanforthGreens.ca and you will be redirected to https://DanforthGreens.ca

Site Health reads:

Your website is using an active HTTPS connection.

An HTTPS connection is needed for many features on the web today, it also gains the trust of your visitors by helping to protecting their online privacy.

Read more about why you should use HTTPS (opens in a new tab)

Specifically, the redirect is in my .htaccess file:

RewriteEngine On

# If HTTPS is off, turn it on.
RewriteCond %{HTTPS} !=on
RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301,NE]

Is there something else I should do, such as completely disallowing HTTP? I wouldn’t want to break links that are coming in to HTTP, just redirect them.

I see that there is a setting available in the DreamHost panel:

AUTOMATIC HTTPS IS DISABLED FOR THIS SITE

[_] Redirect all site content over a secure HTTPS connection.

Disabling this setting will slow the loading of your site and will default to insecure connections. You should only disable this setting if your site requires special redirect settings in your .htaccess file or you want to allow mixed content on your site. (This is not common.) More Info

I’m going to try turning this on.

AUTOMATIC HTTPS IS ENABLED FOR THIS SITE

[x] Redirect all site content over a secure HTTPS connection.

Still no improvement after simple resets and full deactivate-reactivates.

• This reply was modified 3 years, 2 months ago by CharlieHamu.
• This reply was modified 3 years, 2 months ago by CharlieHamu.
• This reply was modified 3 years, 2 months ago by CharlieHamu.
• This reply was modified 3 years, 2 months ago by CharlieHamu.
• This reply was modified 3 years, 2 months ago by CharlieHamu.

I verified in Google Search Console that I had three verified URL prefixes:

1. https://danforthgreens.ca
2. https://danforthgreens.ca
3. https://danforthgreens.ca/wordpress

(With or without trailing slashes, I do not recall.)

And the domain danforthgreens.ca was not verified. I verified the domain using a DNS TXT record, reloaded, reconnected, etc, no success. I deleted the first three, so I only have the domain now, reloaded, reconnected, etc, still no success.

I also turned off my browser’s ad-blocker, but that should only affect AdSense, I think. And I’ve tested on other machines, including a phone, and in incognito mode without Chrome extensions.

• This reply was modified 3 years, 2 months ago by CharlieHamu.
• This reply was modified 3 years, 2 months ago by CharlieHamu.

According to this:

https://github.com/google/site-kit-wp/issues/922

It should not be a problem for WordPress to be installed in a subdirectory.

• This reply was modified 3 years, 2 months ago by CharlieHamu.

Additional information, and a likely path to resolution:

I temporarily changed:

WordPress Address (URL)   https://danforthgreens.ca/wordpress
Site Address (URL)        https://danforthgreens.ca

to be

WordPress Address (URL)   https://danforthgreens.ca/wordpress
Site Address (URL)        https://danforthgreens.ca/wordpress

And this seemed to work. (I got a message about search console needing some time to collect data.) But it messed up the URLs for my site, adding an unwanted /wordpress in the middle of the URLs.

If this is the only solution, I can move my WordPress installation from the subdirectory up to the main directory. But I’d rather not, as there are other non-WordPress files in that directory as well.

• This reply was modified 3 years, 2 months ago by CharlieHamu.

Noting that my URL was

https://www.ads-software.com/support/topic/your-site-may-not-be-ready-for-site-kit-32/

I’ve reviewed every URL from

https://www.ads-software.com/support/topic/your-site-may-not-be-ready-for-site-kit/

to

https://www.ads-software.com/support/topic/your-site-may-not-be-ready-for-site-kit-31/

but not yet found an answer.

Also, I just tested this:

wp eval 'print_r(wp_remote_head("https://sitekit.withgoogle.com"));'

And got an extensive JSON-y looking result that includes both 200 and OK.

• This reply was modified 3 years, 2 months ago by CharlieHamu.
• This reply was modified 3 years, 2 months ago by CharlieHamu.
• This reply was modified 3 years, 2 months ago by CharlieHamu.

Also, with help from DreamHost support, these changes were made:

/home/charliehamu/.php/7.4/phprc

      1 log_errors = 1
      2 error_log = /home/charliehamu/php.log
      3 upload_max_filesize = 600M
      4 post_max_size = 650M
      5 max_execution_time = 500
      6 max_input_time = 500
      7 memory_limit = 500M

And I switched from php7.4 fastCGI to php7.4 CGI.

I’ve modified my copy of Broken Link Checker to allow for bulk archiving.

I guess I should start a new thread for this, so I’ll do that now.

Additional suggestion:

3. Add a short note to the “link tweaks” options: “applies to pages and posts only”.

Suggestions, in case they haven’t already been considered and rejected:

1a. There’s already an option to check-for/not-check-for broken links in comments. In so far as comments “aren’t my responsibility” as a webmaster, would it make sense to not check, and thus not mark as broken, comments when this option is off, and to check … and to mark with a class as broken, comments when this option is on?

1b. My preference: There’s already per-area options for checking links in posts, pages, comments, etc… And there are already separate options for marking links with classes if they are broken, removed, not to be followed. Why not combine these two tabs in a single table (rows for “look for links in” and columns for “link tweaks”.

2. Have you considered rewriting the links with classes (applying the tweaks) at the time the links are found to be broken, rather than at display time? Would this not be more efficient at the time that efficiency mattered?

Thanks. Great plugin!

I’m very happy with the Internet Archive suggestions. Changing topics, a great companion feature would be automatically using the Internet Archive API to archive pages the first time they were discovered to have been linked to.

I’m curious about the reasons for this design. Respect for outside commenters’ integrity of creation perhaps? Or some technical complication?

Yes, all fixed. Thanks so much.

Many things changed in the .htaccess file, but I reckon a key change was on the lines highlighted in https://pastebin.com/m13ce7746

Namely, I had moved wp-content to wordpress/wp-content but the .htaccess file was not updated to reflect this.

Thanks again.

Yes, thank you. I’ll do that and report the results.