Wp-calypso: Jetpack Connect: Clarify Site Address is the location of WordPress and not the Home URL

[BrookeDot]

Steps to reproduce

First create a self-hosted WordPress site with WordPress installed in a subdirectory.
https://example.com/wp -- site URL
https://example.com -- home URL

1. Starting at URL: https://wordpress.com/jetpack/connect
2. Enter the Home URL/Site Address for the site, ie example.com
3. Notice the error "This is not a WordPress site"

1. Enter example.com/wp and be shown the install screen:
   

The install URL did work once I entered the Site URL

What I expected

For the home URL to find WordPress instead of reporting back WordPress was not found.

What happened instead

Was given a message my site was not a WordPress site.

As the above is an improvement on the related #6085 and #6088 I'll close those in favor of this one.

[beaulebens]

At least part of the fix for this should probably be actually accepting the home URL, and then checking the meta data in the page to figure out the site URL dynamically. You can get it from the pingback, EditURI, or wlwmanifest header tags in the source of the document. They're not always available though, so maybe tweaking the wording can help here as well.

[rickybanister]

That url doesn't seem to be a WordPress site would be more accommodating. It would also be good to give a follow-up option. Perhaps a support doc outlining common connection problems or an explicit path to get help.

[stale[bot]]

This issue has been marked as stale because it hasn't been updated in a while. It will be closed in a week.
If you would like it to remain open, can you please you comment below and see what you can do to get things moving with this issue?
Thanks! 🙏