Seo Forum & AI

Search Engine Optimization => On Site Optimization => Topic started by: affinity on 08-30-2016, 07:22:18

Title: Unrecognised HTML in site:URL
Post by: affinity on 08-30-2016, 07:22:18
When I'm checking if a site is indexed with google I'm seeing some unrecognised pages listed e.g

URL/news.html
URL/careers.html

Which looks fine but there is no page or post with these names.

It's a WP site and none of the actual pages or post have permalinks ending in .html

Does anyone know how to get rid off and prevent this?
Could it be resolved by Toolset - Settings: Disallow saving unfiltered HTML in Types customer fields for all users.
Title: Re: Unrecognised HTML in site:URL
Post by: affinity on 09-05-2016, 09:44:26
Quote from: affinity on 08-30-2016, 07:22:18
When I'm checking if a site is indexed with google I'm seeing some unrecognised pages listed e.g

URL/news.html
URL/careers.html

Which looks fine but there is no page or post with these names.

It's a WP site and none of the actual pages or post have permalinks ending in .html

Does anyone know how to get rid off and prevent this?
Could it be resolved by Toolset - Settings: Disallow saving unfiltered HTML in Types customer fields for all users.

Finally got this one resolved and thought I would share the solution here in case anyone else encounters the same thing...

This issue occurs when a website does not have a SSL cert and tries to search for https: , as https will try to only show secure websites ie one with an SSL cert, it will display a website on that server that has a valid certificate. In order for this URL to resolve this an SSL cert would need to be installed on their domain.
Title: Re: Unrecognised HTML in site:URL
Post by: envigodigital on 09-19-2016, 03:59:18
Sounds totally unreasonable solution to me. How are these things connected to SSL is beyond my understanding. What has SSL got to do with particular SSL pages?
:'(
Title: Re: Unrecognised HTML in site:URL
Post by: affinity on 09-19-2016, 08:16:45
Sounded strange to me too, but this is the fix from the hosting provider and it worked!