Skip to main content
10 events
when toggle format what by license comment
Jun 13, 2019 at 3:42 history edited dan CC BY-SA 4.0
Removed link to site. Please note that links to sites are generally frowned upon by the community since they're often associated with spam and self-promotion. Please use only the generic 'example.com` for example URLs.
Jun 11, 2019 at 19:14 comment added Jeff Brower @MrWhite, ISP says the nginx headers come from a static content server fronting an Apache server. .htaccess operation should not be affected
Jun 11, 2019 at 0:27 comment added Jeff Brower 1) "Fetch and Render" is no longer available (read Google's advisories on this). Using the new URL Inspection tool and "View Live Test", page screenshots look normal to me. It's a smartphone bot, so the screenshot is limited -- as you would see on a phone before scrolling down. 2) I gave the pretty URL to simplify. Internally, and on other sites (Texas Inst, Github, Intel, etc) we typically use full URLs. 3) Not a proxy; I will check with our ISP why they are using nginx headers.
Jun 11, 2019 at 0:17 comment added Jeff Brower @Mr White, GSC specifically says "Duplicate, submitted URL is not selected as canonical". If you search "codec wav samples site:signalogic.com" the page is not found or referenced, even though other indexed pages link to it. The forum link I gave in my question clearly describes a canonical algorithm issue. Unfortunately, like some of the larger outfits discussing the problem on that forum, I can't pick up the phone and ask Google to fix it. Thus my original question -- maybe avoiding a URL format that even remotely looks like e-commerce is a way around the problem.
Jun 11, 2019 at 0:08 comment added MrWhite I can't see an obvious reason for this, except that you do have a lot of XHTML validation errors (your page is not XHTML) - you would see a great improvement in "validation" at least by simply switching the DOCTYPE to HTML5. Although I would not expect this to be the reason why Google would drop the page entirely. Have you tried a "Fetch and Render" in GSC? Curious, you linked to /codec_samples, which 301 redirects to the .pl URL - do you use these "pretty"/redirect URLs elsewhere? And you mention .htaccess, but your site returns an Nginx header - is this just front-end proxy?
Jun 10, 2019 at 23:56 comment added MrWhite I don't think it's necessarily a canonical issue. That page simply isn't indexed (as you state). Canonicalisation still requires all the pages to be indexed - it's just that you are setting a preference for which page (from very similar pages) is returned in the SERPs. A site: search should still return the non-canonical pages - in your case it doesn't. A site: search for the title on that page returns another page that links to that page, but not the page in question.
Jun 10, 2019 at 23:11 comment added Jeff Brower @MrWhite, no errors on GSC. No page redirects, mobile friendly. The GoogleBot is just unable to canonical its way out of a paper bag. I don't think content is the issue either, for example this page (signalogic.com/codec_samples) is a very large, unique page. It used to bring in 100s of clicks for us every day. There is nothing else even remotely close to that on our site. Now I cannot get it indexed for the life of me. Re. underlying page structure, no not prepared to change it entirely; that's why my question.
Jun 10, 2019 at 23:03 comment added MrWhite Was Google reporting any errors in GSC? I can't see that changing your URLs is going to help - there is nothing "wrong" with your existing URL structure (as far as the search engines go) - so the problem is likely elsewhere. If Google is picking the wrong canonical page then it's generally because of content, not the URL? Changing the URL structure is not without it's own problems and could itself result in a (temporary) SEO hit. In order to change the URL structure, you obviously need to first change the URLs throughout your entire site - is this something you are prepared to do?
Jun 10, 2019 at 22:36 history edited Jeff Brower CC BY-SA 4.0
wording correction
Jun 10, 2019 at 22:30 history asked Jeff Brower CC BY-SA 4.0