On-page Local SEO

[SSFCU]

I'm wondering how to pull it off on-page local SEO for a financial institution website with 70 locations. However, they are broken in down in regions, which would make it easier to get our hands around. Would a viable solution be setting up regional pages? I don't know about our CMS capability, but it seems like it would be beneficial to have on each regional page aggregate local-centric press releases (example: a volunteer event or recognition) and local announcements such as paper shred days.

Thoughts? Anyone else posed with a similar challenge?

[Ron_McCabe]

Sarah,

I have been working on this exact same problem for another client.  As a disclaimer I am always going for the maximum traffic and conversion for my clients and on the aggressiveness scale I am an 11.

That being said here is what I would recommend.  1) Create a separate navigation for each sub branch.  This would include all the basic information you would on the main site except this should focus on the branch. 2) Manage a blog for each branch with Google authorship set up. 3) Create content about the branch that has the unique feel of the branch along with anything special about the branch or it's employees.  4) Do competitive key word research for each branch and make sure that you include any content that is needed to grab searches from the local competition. 5) I would reflect the unique navigation or location of the information on each branch specifically in your off page SEO.

This approach will get you more local traction while improving the experience and conversion for potential customers for each branch.  This also alleviates the "mega" company feel and helps the branch feel more local.

Ron

[SSFCU]

All of these are do-able but the authorship thing. It would likely be me manning all of the blogs. From my POV, I think the most feasible thing within our construct is aggregating info from the communications department and placing them on each page according to location. As far as one page for each branch, I don't know that it's within our bandwidth and I'd hate to set something up we can't maintain. But I'll definitely bring it up at our brainstorming session tomorrow. Thanks!