The alternative is dedicated engineers

[bhasan01854]

In theory this makes sense, you'll consider SEO projects against all other engineering dependent projects and weigh them against each other when allocating your scarcest resource, engineering time. In practice what happens is a very haphazard investment in SEO. Here's a common way this plays out: You decide to invest in SEO so you open an SEO role, you're able to fill it in 3 months The SEO gets onboarded then does a site audit to generate an SEO roadmap, let’s say say this takes 2 months The SEO is able to immediately pitch a couple projects from their roadmap (no delays waiting for quarterly planning to start or anything) Two SEO projects are committed to in the upcoming quarter, work starts on them in a month and they take another month to actually ship It takes another couple months to see results but both projects end up having a positive impact The above,



very optimistic, timeline is already 9 months long before you see any impact albania phone number database from investing in SEO and assumes: You fill the SEO role very quickly SEO projects are committed to immediately The initial SEO projects produce a positive impact What if this quarter was particularly busy with other initiatives and you couldn't commit to SEO? Or the projects had made an impact but it was difficult to quantify? At minimum the whole timeline would have been elongated, at worst it would be harder to secure engineering resources going forward.


You can have an SEO PM, you can have your own SEO department, you can have the SEO folks live on the product side or the marketing side etc. - all of those permutations can work. The important piece is that you have dedicated engineers to quickly and consistently invest into SEO. As mentioned above, you can swap out “dedicated engineer” for “dedicated analyst” or “dedicated writer” and much of what was said still applies: figure out what resourcing your SEO strategy will require and make a long term commitment to provide those resources.