Search

Newsletter

Get our latest updates. Sign up with your email.

Popular Posts

Avoid Duplicate Typepad Homepages

1 views
Avoid Duplicate Typepad Homepages

I had a client recently ask me about a blog that was using TypePad’s domain mapping feature and it was causing duplicate homepage URLs for the blog. TypePad Duplicate' /> The first was to http://blog.clientsite.com and the second was to http://blog.clientsite.com/blog/. They were concerted that their Technorati rank and linking efforts were being compromised. And, of course, they wanted a fix.</p> <p>I did some digging around it and it turns out that it’s the way the domain mapping was setup in TypePad that was causing the issue. It can be fixed, but there are consequences.</p> <p>In the client’s TypePad account there are actually two blogs, each with a unique URL.</p> <p>1. http://blog.clientsite.com/blog/<br /> <br /> 2. http://blog.clientsite.com/my_weblog/</p> <p>Out of the two blogs above, #1 is setup as the ‘home blog’ meaning that it can be accessed via the main URL (http://blog.clientsite.com/) and the unique URL (http://blog.clientsite.com/blog/).</p> <p>When the domain mapping was setup, the entire account was mapped to blog.clientsite.com, thus the home and unique blog URLs were included.</p> <p>If just #1 was mapped to blog.clientsite.com, then no /blog/ folder would have show up.</p> <p>However, fixing the domain mapping wasn’t going to be easy. The first option was to change domain mapping settings. This would result in all blog URLs changing and the old URLs becoming invalid. The only way to fix the duplicate URL issue, and not break any existing URLs, would be to move the blog to a different sub domain, like weblog.clientsite.com, then setup blog.clientsite.com as a valid hosting account and create 301 redirects for all old URLs to the new URLs. The downside here is that Google may temporarily penalize the new subdomain as it doesn’t have any history.</p> <p>The issue with duplicate homepages is all in how TypePad’s domain mapping is set up. I really wish TypePad would just 301 redirect the home blog URL to the unique blog URL or vice versa. However, that’s not an option that I saw.</p> <p>The client decided to just leave things as they are for now. They are planning on moving away from TypePad so any work now would just be short term. Later this year, we’ll probably move them to a local Wordpress install and ensure that there is only one blog URL.</p> </div> <script> (function() { function initCopyableSections() { document.querySelectorAll('.article-content .copyable-section').forEach(function(section) { if (section.querySelector('.copyable-section__btn')) return; var btn = document.createElement('button'); btn.type = 'button'; btn.className = 'copyable-section__btn'; btn.setAttribute('aria-label', 'Copy to clipboard'); var label = section.getAttribute('data-copy-label'); btn.textContent = label ? 'Copy ' + label : 'Copy'; section.appendChild(btn); btn.addEventListener('click', function() { var contentEl = section.querySelector('.copyable-section__content'); var text; if (contentEl) { text = contentEl.textContent.trim(); } else { var clone = section.cloneNode(true); var btnClone = clone.querySelector('.copyable-section__btn'); if (btnClone) btnClone.parentNode.removeChild(btnClone); text = clone.textContent.trim(); } if (!text) return; navigator.clipboard.writeText(text).then(function() { var t = btn.textContent; btn.textContent = 'Copied!'; btn.classList.add('copied'); setTimeout(function() { btn.textContent = t; btn.classList.remove('copied'); }, 2000); }); }); }); } if (document.readyState === 'loading') { document.addEventListener('DOMContentLoaded', initCopyableSections); } else { initCopyableSections(); } })(); </script> <!-- Tags --> <!-- Correction Form --> <div class=

Suggest a Correction

Found an error or have a suggestion? Let us know and we'll review it.

Share this article

Comments (0)

Please sign in to leave a comment.

No comments yet. Be the first to comment!

Latest News