Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"Inverse" page tracking - to find bad pages #10519

Open
hpvd opened this issue Sep 19, 2016 · 7 comments
Open

"Inverse" page tracking - to find bad pages #10519

hpvd opened this issue Sep 19, 2016 · 7 comments
Labels
c: New plugin For features that probably will not be added to Matomo, but could be implemented as plugins. Enhancement For new feature suggestions that enhance Matomo's capabilities or add a new report, new API etc.

Comments

@hpvd
Copy link

hpvd commented Sep 19, 2016

To make your website better it would be not only interesting which pages are visited, but on the other site:
pages are never or only very rarely visited.

This may have several reasons:

  • they are not visible to the user (design problem)
  • there could be a technical problem (technical problem: maybe only in some browsers)
  • no one needs them (content problem) ...

To find these pages it would be very helpful to have the possibility to find & show them in an automatic way via "Invers page tracking"

one way may be

  • to visit all pages to say "hello - I do exist" to piwik (some kind of crawler)
  • compare these pages with the statistics piwik have from the page tracking
  • show a list of pages never or only rarely used

the next step of this would be
"Invers" Custom Event tracking - to find bad elements/functions #5186

@hpvd
Copy link
Author

hpvd commented Sep 19, 2016

a bad "page" could be:

  • never or only rarely visited (number)
  • visited only for a very short time in average or
  • visited only for a very short time summed up in total

@gaumondp
Copy link

As long as it's possible to remove/diable the feature. If you "only" have 500 pages it's not too bad I presume but I got 11 000 different web pages and maybe 4000 PDF so yes, we have many "unviewed" or low-visited pages over time...

@hpvd
Copy link
Author

hpvd commented Sep 19, 2016

of course it should be only optional - maybe even as an plugin.
In addition it may make sense to have a possibility to restrict (white or blacklist) a path within url...

@hpvd
Copy link
Author

hpvd commented Sep 19, 2016

as first approach crawling could be easily done by using a standard (google-)sitemap.
These are available on most websites and contains the urls of all pages in a standardized xml format

<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <url>
    <loc>http://www.example.net/outsite/black-cats.html</loc>
    <lastmod>2015-09-22</lastmod>
    <changefreq>monthly</changefreq>
    <priority>0.8</priority>
  </url>
  <url>
    ....
  </url>
</urlset>

For this one only need a setting for the url of it (most times it's http://www.example.net/sitemap.xml)

@hpvd
Copy link
Author

hpvd commented Sep 19, 2016

Since the comparison should only be done with very low frequency (e.g.once a month) or on request (e.g. via Button click to schedule it to make it next night) there shouldn't be a big performance problem at all...

@hpvd
Copy link
Author

hpvd commented Sep 19, 2016

In addition a setting for comparison period is needed:
e.g. (not)visited within last month, last year, for all data...
=> hmm maybe this could be directly set by using segment editor?

@hpvd
Copy link
Author

hpvd commented Sep 19, 2016

could e.g. be part of a new plugin which provides a new menu point: "Find the bad"
which contains the functions:
"Invers" page tracking - to find bad pages #10519
"Invers" Custom Event tracking - to find bad elements/functions #5186
"Invers" Content tracking - to find bad pieces of content #10520

@hpvd hpvd changed the title "Invers" page tracking - to find bad pages "Inverse" page tracking - to find bad pages Sep 19, 2016
@mattab mattab added c: New plugin For features that probably will not be added to Matomo, but could be implemented as plugins. Enhancement For new feature suggestions that enhance Matomo's capabilities or add a new report, new API etc. labels Nov 12, 2016
@mattab mattab added this to the Mid term milestone Nov 12, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
c: New plugin For features that probably will not be added to Matomo, but could be implemented as plugins. Enhancement For new feature suggestions that enhance Matomo's capabilities or add a new report, new API etc.
Projects
None yet
Development

No branches or pull requests

3 participants