• Resolved vallo

    (@vallo)


    When connecting the Site Kit it seems it wants to make a new Search Console property instead of using the one already in place. It looks like it has to do something with the property name.

    Current one: “site address”
    Site Kit makes: “https://site aadress”

    How can I choose the one already in place because it doesnt make sense to have 2 properties for one page.

Viewing 10 replies - 1 through 10 (of 10 total)
  • Renee Johnson

    (@reneesoffice)

    Thanks for the topic @vallo ! A few questions to understand what could be occurring:

    1) Is the site being served over https:// or https://?

    2) How is it listed under Settings > General from the WordPress Dashboard (WordPress and Site URL)?

    3) Just to confirm: your Google Account was an owner on the verified https:// version of the property before using Site Kit? If so, which type of property is it: URL-prefix or Domain? Or do you recall how you verified the site before?

    Thanks!

    Thread Starter vallo

    (@vallo)

    Hey again.

    HTTPS has been forced since the beginning of my site.

    In General WP settings its also listed starting with HTTPS, I already tried removing it to see does it take me to the right one when the URL matches with Search Console property. Didnt work.

    Yes, my account was verified before, its a domain property and I verified it by DNS TXT record.

    Tried updating the plugin and problem seems to be the same as @todderz wrote, so the topis can both stay here.

    Plugin Support James Osborne

    (@jamesosborne)

    @vallo I would be curious to know more about this, as you mentioned others have reported the same issue.

    When you added Search Console via DNS verification did you specify the protocol and www in the records you created? (ie. example.com as opposed to https://www.example.com).

    If you use the URL inspection tool from within Search Console you should be able to check how it see your sites canonical URL. Once you confirm everything is in order there can you reset Site Kit and attempt setup again?

    wptools

    (@wpt00ls)

    I have the exact same issue. Plugin version 1.1.1

    I have a domain property already registered in google search console. Name of property is search console is wptools.app. The URLS are https. Website is https://wptools.app

    When I installed/activated/configured sitekit, it added a new property named https://wptools.app/

    Ideally it should show a list of properties from where I can select. It seems like he current use case is catered for users who don’t have any search console property configured.

    I have deleted the new search console property and deactivate this plugin until this is fixed.

    I wouldn’t want anything affecting my site SEO due to this.

    Hope you fix this quickly.

    I am quite excited to take it for a spin.

    Regards,
    Jayant.

    • This reply was modified 5 years ago by wptools. Reason: updated google search console property name
    Thread Starter vallo

    (@vallo)

    @jamesosborne when adding a domain property you can only use “domain.com” and thats what I did. So theres no way I can add HTTPS or www in front of it and it should be automatically covered anyway because thats what domain property does. (To clarify, have never used www anywhere)

    In URL inspection tool it shows up like it should (https://lemur.ee/). Just did reset Site Kit again and deleted the property it makes in Search Console. Keeps making a new one.

    Thread Starter vallo

    (@vallo)

    Update: I just tried activating Site Kit on other web pages I have. Maybe theres a pattern.

    SC URL-prefix property – works.
    SC URL-prefix property multisite – works.
    SC Domain property – doesnt work, makes new property.
    SC Domain property multisite – doesnt work, makes new property (Tried 3 sites – same problem).

    I was hoping its maybe only a multisite problem but Im getting the same error with clean WP installation too.

    Plugin Support James Osborne

    (@jamesosborne)

    @vallo Thanks for the update, very useful with the additional content. There is an open GitHub issue in relation to this which we can work from. I will keep this support topic open.

    I have the exact same issue.
    Why isnt there an option to just select manual a search console profile ?

    • This reply was modified 4 years, 11 months ago by nesoor.
    Plugin Support James Osborne

    (@jamesosborne)

    @nesoor I have responded to your open support topic now.

    @vallo just a follow up that the new version 1.3.0 addresses this issue and supports the domain property configuration in Search Console. We appreciate your feedback as this helped get this implemented.

Viewing 10 replies - 1 through 10 (of 10 total)
  • The topic ‘Site Kit makes new Search Console property when theres one already’ is closed to new replies.