Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the 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 6114

Warning: Cannot modify header information - headers already sent by (output started at /home/aacmain/public_html/wp-includes/functions.php:6114) in /home/aacmain/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /home/aacmain/public_html/wp-includes/functions.php:6114) in /home/aacmain/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /home/aacmain/public_html/wp-includes/functions.php:6114) in /home/aacmain/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /home/aacmain/public_html/wp-includes/functions.php:6114) in /home/aacmain/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /home/aacmain/public_html/wp-includes/functions.php:6114) in /home/aacmain/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /home/aacmain/public_html/wp-includes/functions.php:6114) in /home/aacmain/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /home/aacmain/public_html/wp-includes/functions.php:6114) in /home/aacmain/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /home/aacmain/public_html/wp-includes/functions.php:6114) in /home/aacmain/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1893
{"id":3320,"date":"2020-08-18T22:49:23","date_gmt":"2020-08-18T22:49:23","guid":{"rendered":"https:\/\/thinkendurance.com\/blog\/?p=3320"},"modified":"2020-08-18T22:49:23","modified_gmt":"2020-08-18T22:49:23","slug":"mistakes-to-avoid-when-building-a-website","status":"publish","type":"post","link":"https:\/\/azadvertising.co\/mistakes-to-avoid-when-building-a-website\/","title":{"rendered":"Top 5 Mistakes to Avoid when Building a (New) Website."},"content":{"rendered":"

Whether 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

#5. Typos: content typographical errors, especially with keywords.<\/h2>\n

\"websiteThis issue really is a two-headed monster.<\/p>\n

Typos and properly formatted content.<\/h3>\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

Typos in Keywords.<\/h3>\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

#4. Broken Links throughout your website.<\/h2>\n

\"brokenBroken 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

Main causes for broken links on a website:<\/h3>\n