Hi there. Great question in relation to using another admin path. Site Kit doesn’t require a user to use the default wp-admin path during setup. There have been cases where users have changed their admin URLs after initially setting up Site Kit and this can result in invalid callbacks when reconnecting.
Have you attempted setup so far using a separate admin path other than wp-admin? If you run into any difficulty let me know and I’d be happy to assist.
Is there any way to bypass configuring search console
At present Search Console is used to verify site ownership, but feel free to open a GitHub issue on the plugins repository to allow Site Kit setup without Search Console. I’m happy to assist you if you prefer me to create one for you.
Thanks for the quick response, I’ll look into creating a github issue.
To clarify, the issue isn’t that we use a non-default admin path – the issue is that we use the default one but don’t expose it to the open internet. This doesn’t stand in the way of normal search console verification, since the html tag does make it’s way onto the home page, but it does seem to break the more automated way site kit does it.
Thanks for the clarification. If you want to share the way you’ve setup your admin path restriction I can try and follow the standard Site Kit setup experience while also not exposing the path, before then using the plugin to verify a site with Search Console.
Alternatively if you want to share the same experience you encounter in the form of a video using a service such as Loom or RecordIt I can check for any non standard behavior. You can use this form to share privately if preferred.
As we didn’t receive 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.
