flying-press
domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init
action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/aacmain/public_html/wp-includes/functions.php on line 6114Whether you\u2019re a small business just looking for a brochure website<\/em> or a large corporation with a sophisticated, enterprise-sized site, below is a list of 5 major mistakes to avoid when building a new site (or retrofitting an existing one).<\/p>\n <\/p>\n This issue really is a two-headed monster.<\/p>\n Typos are a signal that your content isn\u2019t up to snuff. We always teach clients to treat your content like a finally tuned engine that is properly constructed in a nested format. Forgetting to pay proper attention to grammar is a common mistake websites make. I think we can all attest to making this mistake, heck this article probably has a spelling mistake or two (darn it grammar.ly). The Point? Always throw your content into M$ Word, then grammar.ly, and then do a final proofreading before posting live. Hopefully doing those three things is enough to catch 90% of your typos.<\/p>\n If typos are bad, making typos in targeted keywords on a page is a tad worse. SEO Hacker has an interesting article about misspelling keywords<\/a> and\/or the many variations of certain keywords in search. I like thinking of content for a page on a website like a chapter in a book<\/strong>. While Google has told us the <H1> tag isn\u2019t as prevalent as before, I still use it like a chapter heading in a book. Put your keyword in the heading and describe what the page is going to be all about. Then genuinely write all about that topic\/item without misspelling the main keyword or variations of it. <\/strong><\/p>\n <\/p>\n Broken links on your site are links that simply don\u2019t work for any number of reasons. Broken links impact a website\u2019s overall link profile (external and internal links that aid in calculating domain authority).<\/p>\n Ahrefs\u2019 blog has a great post about how to find and fix broken backlinks<\/a>. This activity of ensuring a new or existing site doesn\u2019t have broken links should fall under the site maintenance bucket. Scanning and fixing broken links should happen monthly or at least quarterly.<\/p>\n <\/p>\n If you\u2019re asking, \u201cWhat is schema?<\/a>\u201d<\/strong> you\u2019re probably not alone. There are a lot of us around that are still unaware of schema. Schema is roughly ten years old now, and it\u2019s really starting to pick up steam with search engines. Schema is an additional content tagging technique that helps inform search engines exactly what the content on a page is all about. <\/strong><\/p>\n The easiest example to illustrate how schema works is with a blog recipe page. Google may or may not be able to figure out that a specific blog post is actually a recipe, but imagine if you could tell Google’s search engine that it\u2019s a recipe and to treat it as such in search results.\u00a0 That\u2019s the power of schema.<\/p>\n Google put out some developer guidelines for schema they \u201cofficially\u201d support<\/a> (they call it \u201cstructured data,\u201d these words are synonymous). Their guide instructs how to format schema code for Google\u2019s search engine. If a website is powered by WordPress, there are many schema plugins that automatically implement schema<\/a> coding (although some additional manual selections may be needed from time to time).<\/p>\n The point?<\/strong> After ten years schema is here to stay, and it really helps search engines take the guesswork out of trying to figure out what your website\/webpage is all about.<\/p>\n <\/p>\n It\u2019s been a while since Google\u2019s search engine began considering a website\u2019s mobile layout first (over desktop). Great info from Moz on mobile-first search engine results<\/a>. And responsive design methods really started to catch on when browsers started supporting CSS media queries (around 2008\/2009).<\/p>\n It really is as simple as it sounds. Your website works perfectly on a mobile phone. Think of how you hold a phone in the palm of your hand. One usually surfs the web in a vertical (portrait) layout. You surf twitter in portrait mode. You scroll through Instagram in portrait mode. Everything is done on a phone in portrait mode (except watch videos). A website made for mobile first will display the content of the entire website (and all its pages) perfectly on a mobile device in portrait mode. Seems simple right? Unfortunately, it\u2019s not. Most website designers build websites for desktop first. And a site built for a wide layout will look too small and usually break on a phone.<\/p>\n Design your site for a mobile portrait layout first.<\/strong><\/p>\n <\/p>\n <\/p>\n <\/p>\n Probably one of the worst mistakes for any website (new or old) is ignoring SEO. SEO is a marathon, not a sprint.<\/strong> The sooner you start training and taking part in marathon after marathon, the sooner you\u2019re in the race for good! At the very least you need to do these three things on every page of your website:<\/p>\n This might be a daunting task if you manage a large website with many pages. This still<\/strong> needs to be done.<\/strong> Your title should be 35-45 characters long (I try not to go longer because of mobile phone viewports even though technically you can push it to roughly 60 characters). Try not to go further than 140 characters (including spaces) on the description. If you can\u2019t tell people what you\u2019re page is about in the original length of a tweet, you should probably break up the page into multiple pages (or try again).<\/p>\n Images should be optimized on three levels:<\/p>\n The image filename should describe the image (if possible). So if you include an image of an apple on a page about \u201chow to eat an apple,\u201d name the image something like: eating-an-apple.jpg. Or, if you\u2019re on a large content management system, something like eating-an-apple-8283238923.jpg is fine as well.\u00a0 Do the best you can.<\/p>\n No image on a website should exceed 150kb (unless your site is a library of desktop wallpapers, or photography). Icons, background images, thumbnails, etc. try to keep all your images below 150kb. Use online compression tools, photoshop, whatever you need to in order to get that file size down.<\/p>\n With an HTML <img> tag, you can add an \u201calt\u201d attribute to describe what the image is about. So if we named our previous image eating-an-apple.jpg, <\/em>we might describe the image further in the image alt tag. E.g. <img src=\u201d.\/img\/eating-an-apple.jpg\u201d alt=\u201dHow to eat an apple \u2013 granny smith green apple\u201d \/><\/em>.<\/p>\n <\/p>\n Our SEO Audit and Analysis<\/a> checks over 100 things so you might be asking yourself, \u201cWhat about content?\u201d or \u201cWhat about site performance?\u201d or \u201cWhat about Social Markup?\u201d etc. etc. etc. So why focus on meta data, image optimization, and tracking?<\/strong><\/p>\n The truth is, these are things that I believe you should have at a minimum and to start with<\/u><\/em>. So if we\u2019re starting at zero, start with this.<\/p>\n So why Google Analytics and Search Console? <\/strong>Both are fantastic tools to continue making your site great. Understand what users are consuming, how they are interacting on your site, and what else should fixed on your site (new or old). Setup your Google account, embed the analytics code on your site, and setup search console at Google.com\/webmasters<\/a>.<\/p>\n <\/p>\n Do you agree? Disagree? What is your biggest mistake you\u2019ve ever made on a new or existing site?<\/p>\n <\/p>\n If you liked these tips, please consider subscribing to ENDURANCE:<\/strong><\/p>\n <\/p>\n Subscribe to more tips like these by following the #ENDURANCEtips<\/strong><\/span> hashtag. This specific article was shared using #WebsiteTips<\/strong><\/span> & #MarketingTips<\/strong><\/span><\/p>\n <\/p>\n#5. Typos: content typographical errors, especially with keywords.<\/h2>\n
Typos and properly formatted content.<\/h3>\n
Typos in Keywords.<\/h3>\n
#4. Broken Links throughout your website.<\/h2>\n
Main causes for broken links on a website:<\/h3>\n
\n
#3. Forgetting about Schema (aka \u201cMicrodata\u201d or \u201cStructured Data\u201d).<\/h2>\n
#2. Not implementing your site for Mobile layouts FIRST<\/strong>.<\/h2>\n
What is a website that considers a mobile-first layout?<\/h3>\n
#1. Ignoring Search Engine Optimization (SEO).<\/h2>\n
A. Ensure Meta Title and Meta Description are filled out.<\/h3>\n
B. Optimize images.<\/h3>\n
\n
Optimize an image filename<\/h4>\n
Optimize image file size<\/h4>\n
Optimize image alt tag (aka alt attribute)<\/h4>\n
C. Setup Website on Google Analytics and Google Search Console.<\/h3>\n
The biggest mistakes to avoid on your website\u2026<\/h2>\n
\n