![WebmasterDragon.com](data:image/svg+xml;utf8,<svg xmlns="http://www.w3.org/2000/svg" width="350" height="110"><rect width="100%" height="100%"><animate attributeName="fill" values="rgba(153,153,153,0.5);rgba(153,153,153,0.1);rgba(153,153,153,0.5)" dur="2s" repeatCount="indefinite" /></rect></svg> "WebmasterDragon.com")
![Screaming Frog results showing similar URLs](data:image/svg+xml;utf8,<svg xmlns="http://www.w3.org/2000/svg" width="538" height="500"><rect width="100%" height="100%"><animate attributeName="fill" values="rgba(153,153,153,0.5);rgba(153,153,153,0.1);rgba(153,153,153,0.5)" dur="2s" repeatCount="indefinite" /></rect></svg>)
It’s not even April and I’ve made another foolish mistake on this site. Call it my own version of “March Madness” and quasi duplicate URLs. It’s an error of my own making and I have no one to blame. Chances are it may be one that you have too. Fortunately, I’ve discovered this one early so it will be easier to fix.
server-errors
The Case for Examining Your URLs
![404 error page example](data:image/svg+xml;utf8,<svg xmlns="http://www.w3.org/2000/svg" width="250" height="250"><rect width="100%" height="100%"><animate attributeName="fill" values="rgba(153,153,153,0.5);rgba(153,153,153,0.1);rgba(153,153,153,0.5)" dur="2s" repeatCount="indefinite" /></rect></svg>)
Sometimes, it’s the small items you don’t know about that bite you. After a poor support experience with my first web hosting company, I decided to move my site. I talked to the new company’s sales rep beforehand and felt confident I made the right decision. Except, there was one question I didn’t even know to ask about until various URLs showed 404 server errors. It’s what I call the “capital crime”.