: Link to full domain on each website menu - does it affect Analytics or SEO I am looking into creating a web portal for my website. The web portal will be inside the directory of the main

@Debbie626

Browsers and search engine fulfill the URL with the rest of the data. If you use page1.html, on www.example.com/dir1/, they read a link for www.example.com/dir1/page1.html. If you use /page1.html, they read www.example.com/page1.html. And, if you use //www.example.com/page1.html, they read www.example.com/page1.html.
Problem with that? The first one, subdomains / subdirectories / another separation for sections and/or languages. Second, if you have your page on http / https, links force the user to go to one protocol and not continue on the already used one.

For SEO, there's better if you doesn't have duplicate content. That's is, if your page are on example.com and example.com, do a 301 redirect from one domain to another. On the another one, use links as you prefer. But, if you have two pages, for example, www.... and www...., use relative links always, except for the login page (always load login page on https if you can), and, also, use canonical meta for specify one protocol / domain as "principal".

Vote Up Vote Down

@Nimeshi995

What you're describing are absolute links (https://example.com/page1.htm) and relative links (/page1.htm).

It really doesn't make any difference for SEO or analytics.

The advantages/disadvantages of each approach are only significant when you move a website to a different location.

Vote Up Vote Down