One of the other places I see SEOs stumble is not around creating the recommendations but in getting them implemented on the website.

We recently published a guide to SEO implementation which provides a framework for how to present and track implementations. If you have already collected your recommendations, check out that guide on how to implement them.

Whether your SEO strategies are high or low effort on the impact grid, they will only be impactful if you can implement the recommendations—which requires team buy-in, developer support, or a powerful SEO implementation tool like PageImprove.

Use PageImprove to Implement SEO Optimizations on Your Own
PageImprove is an innovative new tool that enables SEOs to implement many of the most critical SEO changes through a browser extension. Through manipulating the Document Object Model (DOM), SEOs can make title, meta, copy changes, links, and other html attributes directly into a page without CMS access. The Document Object Model is a term that describes the compilation of HTML, CSS, and JS that create the final webpage.

If all that sounds technical, all you really need to know is that you’re making instant changes that Google will index and visitors will see. You do need to install (or have your dev team) install a javascript snippet on every page of your site, but after we looked into it, our team had no reservations about the safety of the code or worries that it would slow the site, so install with confidence.

Making recommendations is great, but getting them implemented is even better. PageImprove allows us to move past the dev queue and get our work implemented faster, leading to faster results.

Do Agile Technical Auditing
In the world of web/app development there are two models for how teams work. Waterfall and Agile. The Agile methodology is built around sprints. In SEO we have traditionally worked in more of a waterfall approach where a bunch of recommendations are dumped on a client or dev team’s desk while we move onto other audits or optimizations.

The waterfall approach may be simpler than Agile, but you give up the ability to prioritize high-impact changes. Try a more agile approach where you are constantly crawling and identifying key priority fixes.