Forum Moderators: open
I am having trouble trying to write an seo plan of action for a site. I need to tell the person everything that is wrong with their site and submit the plan to them. The proposal is done. I am just doing the consultation part of their site but I am not sure how to format the document for them. I can tell them everything that is wrong with their site and how to fix it. I am not sure how to put that into writing. Any suggestions?
1. build your case from ground up (they'll likely want to know "why")
2. make sure you index your content so they can see at a glance your organization of thought/content
3. use screenshots/graphics to demonstrate your points-will help greatly in communication
4. start this process by creating a bullet-list of your entire proposal first and then build out each section.
I am having trouble trying to write an seo plan of action for a site. I need to tell the person everything that is wrong with their site and submit the plan to them. The proposal is done. I am just doing the consultation part of their site
Before going any further, this isn't so much a content issue as a business/seo issue. Couple of questions:
>>You say the proposal is done.
Question: Have they accepted the proposal and agreed to go ahead with your services?
>>You say you're doing the consultation part and need to give them a detailed plan of what the site needs to be SEO'd
Question: Have they paid you for this consultation, for telling them all that's wrong with a plan of action to correct?
I am about to write up my consultation and they will pay when they get it.
I am having a hard time writing the consultation because I am not sure on the proper format that I am supposed to give them when i write up the consultation.
Second - we put action points that are urgent in a separate box - highlighting what they need to do. Some clients get too bogged down to take it alkl in, so once they'v trusted you, the action points are all they care about next.
One of our largest competitors also focuses on the quick wins. I don't, myself, because invariably (well - often) changing the architecture is hardly a quick win.... but is the most impotant foundation. I can see how this is appealing to clients though - so you might consider that.
Take out excessive data and put this into an appendix.
The executive summary is the MOST important section of the site. Right at the start - probably half a page long.
Try not to completely slag off the web developer that is going to have to make the changes. (I Learnt that from doing clinics at Pubcon!)
For clients, there is a thing as too much information - especially for smaller clients it can be useful to try and keep it as simple as possible.
If they are using an external web developer to make changes to their site, you might want to create a seperate document for them - just a basic "to do" list of technical changes. There's no need to give the web developer all your goods! ;)
MG
1) Overview - provide overview of website and situation (amount of traffic) and proposed goals
2) Spell out the SWOT - strengths, weaknesses, opportunities and threats
3) Propose recommendations to achieve goals from your perspective
4) Outline deliverables and expectations
5) Spell out costs