Idea for the new on-page tool in Pro

[chrwald]

Hello,

I just ran about something, which looks like a minor change (at least to me, but i totaly get, that what looks like a minor change to the outsider might in fact be a big deal from the developers view) but could easily enhance productivity with the new onpage-tool.

In the overview of tracked on-page reports, I think it would be a great idea, to show the number of unsolved suggestions next to the score. Additionally, I'd love to flag some unsolved suggestions on a single page as "ignored". Why should I ignore a suggestion? For example

• I'm working for a customer, who is using a pretty old e-Commerce System. Therefore there is no possibilty to easiely add canonical tags.
• Also on some pages, it is not feasible to get below the 100 links per page threshold.
• On Pages, that list all products of a certain brand, I naturally get the "avoid spamming" suggestion regarding the brand-name
• Some Pages adress Keywords with german Letters like ÄÜÖß, which cannot be found in the page URL (while Google does get that "über" and "ueber" are the same thing).

So there are cases where I can't - or simply don't want - to solve the suggestion. Now it happens almost every week to me, that I see keyword ranking, lets say, at 7 with a score of something like 87. The usual instinct is to click the report to look for the last tweaks. Often then I realise, I checked this report few weeks ago and can't or won't do anything regarding the remaining suggestions.

If it would have something like "3 unresolved suggestions (+ 2 ignored)" standing next to each score in the reports overview, it would be my personal usability dream come true - since the number of open suggestions is more important to me then the score.

To make it even more aweseome, add a simple filter: "Only show Reports with not-ignored unresolved suggestions". Whoohooo, that would make you one happy customer!

Maybe that is something, many people would enjoy to see in an update.

Cheers, Christian

P.S. sorry for my bad englisch - hopefully you got the idea.

unbenannt-3.jpg.html

[jon.white]

Thank you very much.  This is very helpful.  I am going to write up some requirements now around dismissible rules.  No promises on when, but I will add it to the backlog.

Are you interested in helping out with future product feedback or research? If so please email me at jon@moz.com and I will add you.  Thanks!

[chrwald]

Hello Jon,

thank you for the fast answer. Regarding your questions:

First I was thinking about ignoring suggestions on a single page level, which I think should be an option. But your question got me thinking. Additionally telling the system to ignore this for the whole sub- or root-domain would be nice too. An example for each case.

• My target keyword for a page is something like "Überclothing for Hômmes". To be able to ignore the URL-suggestion for this page would be nice, but ignoring it on a domain-level not so much, because on other pages I might target keywords that just contain ASCII-Symbols like "funny shoes" and therefore the suggestion would still be valuable.
• The suggestion for using a canonical tag, url-length or static urls on the other hand could be a domain-wide limitation comming from a CMS or eCommerce-System, so I'd prefer not to ignore it manually for every page.

To wrap it up: The best solution in my oppinion might be something like you are doing allready when I'm hiding an insight. There, when I hide one insight, the page asks, if I'd like to ignore ths insight forever. This might be a good idea for ignoring suggestions too. Whenever someone chooses to hide a suggestion, the page could ask, if this should be done for this certain page (as default) or all pages on this sub- or rootdomain.

Regarding the influence of ignoring suggestions to the score: One could think it would be nice to have a score relativ to the non-ignored suggestions, where e.g. 82 points is 100% of all open suggestions and therefore the percentage would be more interessting then the raw score.
But that might get confusing in some cases.

So at least I personally would be fine with this not having any impact on the score at all. Like I said in my first post: I don't care as much about a score as I care about actionable suggestions. So If I see "allright, thats just a score of 75, but thats as good as it can get right now", that would be sufficient - and maybe even a strong reminder, that I might think about implementing features like speaking urls or canonical tags into the cms/eCommerce-System, which is currently holding me back.

Cheers, Christian

[jon.white]

Hello there!

Firstly - thank you for the suggestion! And the thoughtful and detailed way in which you wrote it.

I have some good news for you - we are actually working on your first suggestion right now - this should be live very soon.

For your second suggestion, this is not on our roadmap, but I would love to get a bit more context from you:

• would you expect to be able to ignore for all pages, or individual pages? Why?
• would you expect your 'ignore list' to affect the score? Why?

Thanks again!

Jon