I ran the W3C link checker and everything was fine except: --------------------------------------------------- h*tp://www.nonilinks.com/images/spacer.png What to do: The link is broken. Fix it NOW! Response status code: 404 Response message: Not Found Lines: 21, 27, 68 --------------------------------------------------- I can't figure out where on my site that is and how to fix it. I'm not a programmer and this is my first site. I'm using Godaddys website tonight software which kind of stinks, but its working to get my message out and I've actually had several sales from the site. I now find myself staying up way to late everynight tinkering with things trying to make them perfect. If anyone can help, I'd appreciate it. Thanks, Tony
If you are using DreamWeaver (like I do) if your template was based on a .png, it sometimes keeps that information inside the template. This information will sometimes(sometimes since my 404's were random) be referenced by the server, and if you have the file only on you dev server, you get your error. Check for this and correct as necessary. hth, tom
TommyD, he said he's using GoDaddy's online webpage building software, not Dreamweaver. nonijuicer, download and run the freeware Xenu from http://home.snafu.de/tilman/xenulink.html -- it will not only tell you which links are broken but where to find the broken links. Xenu Link Checker (freeware) However, no matter what you use, you will need the capability to edit the HTML for the page in question. If you can't, it may be that it isn't critical or necessary -- this is just a spacer around some part of the page. Yes it will generate a 404 error but as long as the page displays the way you want it to display, your visitors aren't going to care and it won't affect spidering your page if that's the only error.
OH! I didn't know what that was, thought it was a hosting package or tool, not an authoring package. Well then........ Ah ........ Scratch what I previously said. New idea: since this might be an error not generated via a clicked link, a spider might not find it, but a good log reader might find where it is referenced when the error is read. Next idea: If your site is small, open each page, view source and do a search for the file name. Maybe this GD authoring tool has text search in the source codes for the file name(DW does). hth, tom