Tools
SERPerator
Live test to see Google mobile and desktop visibility - PPC, SEO & Other.
Page-oscope
Live test to see competitors landing pages in any country - Mobile & Desktop.
App Rankalyzer
See live Google App Pack Ranking results by country and keyword.
SERP Datalyzer
Track search result visibility over time. See visual search results images & parsing about rank, pixels from the top and more.
Page Datalyzer
Track landing pages and page code over time - for you or a competitor.
App Datalyzer
See how your apps and competitive apps rank for keywords in the Apple App Store and Google Play - track in any country and language.
API Integrations
Add Page-o-Scope or SERPerator utilities to your site!
Resources
Request Consulting
Request the consulting proposal from our team of ASO and SEO experts.
Request Training
Reach out to our team for bespoke training.
Request a Tool Demo
Request a guided walkthrough of our leading rank tracking and page testing tools.
Blog
Catch up on our latest insights on industry news and theories.
Webinars
Glossary
Click here for clarification on our terminology.
Help
FAQ
If you have a question about our tools, read here for our frequently asked questions.
Contact Us
Reach out to our team for support.
About MobileMoxie
Use Cases
Brands
Find out about the way brands use our tools to stay ahead of their competitors.
Agencies
Find out about how our tools help agencies win more business.
Analysts
Find out about how BI experts use our tools to tell a story with data.
When a URL changes, webmasters can use a 301 or 302 redirect to ensure that anyone who requests the old URL is redirected to the new URL. In some cases, a URL may change multiple times, such as, from with the ‘www’ to without, and then from ‘HTTP’ to ‘HTTPS’ and then maybe a directory change in the file structure. Cases like this may be described as having multiple hops, if the user requests the original URL, is then redirected to that version of the URL without the ‘www’ then redirected again to the ‘HTTPS’ version of the page, and then to the location in the new directory. It would be better for the user, to minimize load time, if the redirects or ‘hops’ could be minimized. It is best to write redirect logic in the ht-access file that anticipates the middle hops, and includes them in a single rule – reducing this scenario from 3 hops to just 1. This can also be an important strategy for managing link value, since Google has said that link value does not pass through more than about 2 or 3 hops.
Related Terms: