Thanks for reaching out. Site Kit requires a site to be online in order for Search Console to connect with and verify ownership of a domain. If you already have a live site with Site Kit successfully connected and you’re looking to display data from this live (production) site on a local WordPress install using a service such as WAMP this will soon be possible.
You may also wish to keep your eye on our website, with instructions on using Site Kit in a staging environment provided.
Once we’ve made changes to allow for data to be used from a live site to a local WordPress install we’ll update this documentation accordingly.
Let me know if you have any questions on this.
Hi James,
Thank you for the quick reply.
Could you please elaborate on what you mean by ‘live site’?
I believe my site classifies as a live site judging by the information you have given. You also mention a site must be live in order to verify ownership of a domain through Search Console, which I was able to do without issue.
Access to the site is not limited to my local network. The site is public and accessible to anyone.
Please let me know where I should go from here.
Thank you for your help!
Thanks for the clarification. In that case if you want to share your Site Health information here or privately via this form I’d be happy to check your current setup. I assumed you were only using WAMP locally.
I just shared the Site Health information through the Google Form.
Again, thanks for your help!
No problem at all, thanks for sharing. From inspecting the details provided the URL you provided isn’t accessible, indeed the parent domain along also seems down.
Let me know when this is live with no restrictions and I can check once more. Until then it’s normal that you won’t be able to proceed with Site Kit setup.
My apologies, I had taken the site down for a few days.
It’s now back up and live.
Thanks for the update. It looks like your WordPress install in contained within a subdirectory that contains a space, which is unusual. I’m also having further issues consistently accessing your site at present.
Best practice would be to not include spaces or capital letters when naming directories when it comes to hosting your site. Do you have plans to change this?
@buckyjunior As we haven’t received a response, I’ll mark this as resolved. Feel free to open a new support topic if you continue to encounter issues, or reopen this topic and we’d be happy to assist. Thank you!
Apologies for the dead topic, I haven’t had the chance to work on the site since I last opened this support topic.
Thank you for your help, James! The space in the subdirectory was causing the problem!
I do, however, have a new problem. After Site Kit passes through the setup procedure, I receive this error:
Unknown Error (code: cURL error 60: SSL certificate problem: unable to get local issuer certificate). To fix this, redo the plugin setup.
I am currently looking into this to find a solution.
-
This reply was modified 2 years, 11 months ago by
buckyjunior.
Glad to hear you were able to solve the initial issue.
In relation to the “cURL error 60: SSL certificate problem” this is a configuration issue issue with your WAMP setup. Unfortunately there is nothing we can do on the plugin side that will allow you to proceed. Below is a resource another user used to correct their configuration:
https://martinsblog.dk/windows-iis-with-php-curl-60-ssl-certificate-problem-unable-to-get-local-issuer-certificate/
Can you let me know how you get on after checking your own cacert.pem file?
Update.
I managed to solve the problem by reading through this Stack Overflow post.
For future reference, and for anyone that may end up with a similar issue, these are the steps I followed to fix the problem:
1. Download the cacert.pem file from here.
2. Double check that ‘mod_ssl.so’ is present in C:\wamp64\bin\apache\apache(version)\modules
3. Add the cacert.pem file to C:\wamp64\bin\php\[PHP Version]\extras\ssl
[NOTE: For WAMP users, to identify what PHP version is being used, left click the WAMP icon in the tray, and find ‘PHP’. Next to ‘PHP’, there is a number. This is your PHP version. In the case that C:\wamp64\bin\php\ has multiple versions, use the version you’ve identified to be active.
4. Left click the WAMP icon in the tray, hover over ‘PHP’, and click ‘PHP.ini’ Navigate to the ‘[curl]’ heading. For me, this was close to the bottom of the file. Under the [curl] heading, there should be a line that reads:
;curl.cainfo =
Change this line to recognize the cacert.pem file you added in Step 1. Specify the directory of the cacert.pem file:
curl.cainfo = “C:\wamp64\bin\php\[PHP Version]\extras\ssl\cacert.pem”
[NOTE: MAKE SURE TO REMOVE THE SEMICOLON]
These steps worked for me. For additional troubleshooting, check out the original Stack Overflow link as the original post has additional information.
Many thanks for sharing the additional insights which allowed you to proceed with your WAMP install. Hopefully this will be of use to others also.
As you’re not able to proceed can you confirm you’re also able to setup the other Site Kit modules / Google services?
@buckyjunior Just checking in here. Have you been able to setup the other Site Kit modules and Google services?
All other Site Kit modules function properly and I have had no other issues.
Again, thank you for your help.
Great, glad to hear! Please do feel free to leave a review – we’d love to hear your feedback on the plugin.
