Dear freelancers,
after the first round of bids, I realized one simple thing: many of you do not read the technical task at all. At most, you skimmed through a few lines, and then the standard set begins: subscription fee, monthly support, SEO for six months, a million traffic, and a bit of magic on top.
Let me clarify right away, so there are no unnecessary fantasies: I do not need monthly support, I do not need a subscription fee, and I definitely do not need stories about how you will bring crowds of traffic in six months. This is project work.
The task is simple and specific: prepare the project website for production and perform basic SEO optimization according to the technical task.
What is included in the work:
— create the website structure according to the semantics;
— prepare a content plan;
— fill the website;
— create internal linking;
— write meta title, description;
— and in general, do everything that normally and logically follows from the technical task.
So you do not need to sell air. You need to open the technical task, read it carefully, and provide a proposal based on the essence.
It is also amusing that some even give dislikes for a “bad technical task.” Dear ones, if after reading you still think that the technical task is bad, then perhaps the problem is not with it. Perhaps you should first sit down at the table and learn to read, and only then respond to projects.
Once again: this is project work. One-time. For a specific technical task.
Therefore, I would appreciate it if before sending a template “sheet” about strategies, promotion, and the bright future of the website, you still read what exactly needs to be done.
