Welcome to the Q&A Forum

Hi Myron123, Thanks for your question! Did you see Gaston's thoughtful response? If it helped answer your question, please mark it as a "Good Answer." If not, please give us a detailed update so we can help. Thanks! Christy

Thanks Eli

Thanks Donna,  I've already tried switching back to the default theme and no difference. However your link does show that Wordpress itself adds the canonical link to every post and page by default so that'll be where it's coming from, rather than the theme. Thanks.

Hi Christy, This is not resolved yet. Thanks Rajesh

Thanks for the response. Looks like we have 55 in search console that I am working on fixing now (mostly things I drafted in CMS) Would I need to add anything I don't want indexed anymore to robots.txt? I assume that some of the incomplete 301's might stem from this?

Hi there, Sam from Moz's Help Team here! You can find the keyword difficulty, and SERP analysis, right here in Keyword Explorer: https://moz.com/explorer/keyword/overview?locale=en-US&q=cat, along with keyword suggestions. You can also find the difficulty and SERP analysis in the 'Analyse a Keyword' section of your campaign, and add locally tracked keywords with a variety of search engines in the 'Tracked Keywords Overview' of your campaign. https://moz.com/help/guides/moz-pro-overview/rankings/add-and-manage-keywords/local-keywords If you'd like a more thorough runthrough, you can sign up for our Intro to Moz webinar here. In this webinar, we’ll cover how to set up your account and gain a thorough understanding of Moz Pro’s capabilities. If there’s anything else you need, just let us know!

Hi Zack, I think your concern here is valid (your render with Screaming Frog or any other client is unlikely to be precisely representative of what Googlebot will see/index). That said, I'm not sure there's much you can do to eliminate this knowledge gap for your QA process. For instance, while we have seen Googlebot timing out JS rendering around the ~5s mark using the "Fetch & Render as Googlebot" functionality in Search Console (see slide 25 of Max Prin's slide deck here), there's no confirmation this time limit represents Googlebot's behavior in the wild. Additionally, we know that Googlebot crawls with limited JS support - for instance, when a script uses JS to generate a random number, my colleague Tom Anthony found that Googlebot's random() JS function is deterministic (returns a predictable set) - so it's clear they have modified the headless version of Chrome they use to conserve computational expenses in this way. We can only assume they've taken other steps to save computing costs. This isn't baked-into Screaming Frog or any other crawling tool. We have seen that with a 5s timeout set in Screaming Frog, the rendered result is pretty close to what "Fetch & Render as Googlebot" functionality demonstrates. And with the ubiquity of JS-driven content on the web today, provided links and content are rendered into the DOM fairly quickly (well ahead of that 5s mark), we've seen Google rendering and indexing JS content fairly reliable. The ideal would be for your dev team to code these pages to degrade gracefully - so that even with JS support totally disabled, navigation and content elements are still rendered (they should be delivered in the page source, then enhanced with JS, if possible). Failing that, the best you're likely to achieve here is reasonable confident that Googlebot can crawl, render and index these pages - there'll be some risk when you publish them to production. Hope this helps somewhat - best of luck! Thanks, Mike

Hi James, I always prefer shorter over longer URLs. They look a lot cleaner which I believe Google likes. However saying that, I don't think there is a preference over one or the other as long as your website structure is SEO friendly. What are the pros to the longer URL for you? Cheers, Casey

No this is ok. The old site will stay in the index for a few more weeks. Can you identify if the missing traffic is all organic?

I can completely see where your coming from and agree! Thank you!

Hey there! Tawny from Moz's Help Team here.  Unfortunately, there's no way to transfer settings between Campaigns. The only workaround is to set up a fresh Campaign with all the same settings manually — there's no way to do this automatically. Sorry about that! ​If you have any more questions, feel free to reach out to us at help@moz.com and we'll do our best to help you out.

Hey Marc, thanks for contacting us! So one thing that might explain the discrepency is that MozBar reads on page elements, where the crawler is looking at the raw source code.  Can you send in an email to help@moz.com with some example URLs that we can check out? thanks!

Thats great thanks for the help

Hi Andrew, Thanks for jumping in here! Did you see Tomvl's response to your question (below)? Just make sure. Thanks for all your help in the forum! Christy

Hi there! Sam from Moz's Help Team here! Could you please pop an email over to help@moz.com, along with the name of the campaign/URL you're observing and the specific area of the tools in which you're looking so we can ensure we're getting you the answer you need? Looking forward to hearing from you!

Thank you. that was an eye-opener.now i understand now that the SEO content and UX on a page can be great but if the interaction on the site is not satisfying to Google compared to competitors then is not enough.

What a kind offer, Ben. Hopefully, if Bcallegary hasn't already taken steps on this step on their own, they will see your post here with such a nice offer to help.

Have a page for the pillar topic and one for the sub topic if you have the word count to justify it. Otherwise sub topics can be H2s if you have two separate pages I would avoid keyword cannibalization were possible. Keep your keywords on the page that target them. However it may be necessary to talk in the context of pillar content. If you do mention the Pillar keyword, make it a text link to the pillar page. That way google will attribute the use of that word to the pillar page when ranking - and it will in fact strengthen the pillar page. Does that make sense?