Frequently asked questions

Four things set the figure: how many different page templates you need, whether we build the design from scratch, whether we write custom software for you, and who writes the text. We don't publish a price list on the site, because a number quoted without knowing the scope always covers either too much or too little. Give us one call to go through those four and we'll send the written quote the same day. What each package covers is listed item by item on /paketler.

Because the quotes aren't describing the same job. One may be for installing a ready-made theme, another for an interface and custom software built from scratch. Before you compare them, ask both sides four questions: is a theme being used, how many revision rounds are included, who writes the text, and who keeps the code after handover. If the answers don't match, there is no point lining up the numbers.

The fixed ones are the domain renewal and the hosting fee. The SSL certificate is free on most setups, so it doesn't become a separate item. The rest is optional: a maintenance agreement, monthly search engine work, an advertising budget. We go through which of those you actually need in the first call and write each one into the quote as its own line.

No. Your site runs without one and you change the content from the panel yourself. The difference is this: with maintenance, the updates, backup checks and security patches happen without you noticing. Without it, you call us when something goes wrong and pay per job.

That comes down to the cost per click in your sector, and sectors differ a lot. Once we open your account and look at your keywords, we can give you a realistic range within a day. One thing to settle from the start: the advertising budget goes straight to Google from your own account, and what we earn is the management fee.

Usually yes, but the order has to change. On a tight budget, working on a ready-made foundation instead of a design from scratch and putting the money into content and visibility gives a better result. Spending the whole budget on the build and leaving the site somewhere nobody can find it is the mistake we see most often.

The calendar is set by how fast content and approvals come in, not by how fast we write code. Where a company has its text, photos and product details ready, the job finishes noticeably earlier. After the discovery call we give you a dated schedule along with the scope document, and we mark the steps that carry a risk of delay on it. We tell you the estimate in the call; writing a general figure here would only mislead you.

Revisions apply at the design stage. We put the number of rounds in the written quote once we've talked through the scope; we don't publish a fixed number on the site, because page count and design depth change it. One round means the feedback you've gathered gets applied in a single pass. Requests that arrive piecemeal count as separate rounds, which is why we ask you to collect everyone's comments and send them in one go. A design change after coding has started becomes an extra item, and not out of stubbornness: rebuilding a section that's already coded takes longer than drawing it did.

Either of us. If you supply the text, we handle the layout and the search engine side of it. If you want us to write it, it's priced as a separate item: we hold a briefing session with you and put the draft to you for approval. Technical product detail has to come from you in every case, because there's no writing it correctly without a source.

You talk directly to the person doing the work. We don't put an account manager in between. In return, we ask you to name one decision maker on your side. When approval has to pass through three people the process stretches out; we've watched it happen too many times.

A shoot isn't included in the quote, it's planned separately. If you have no usable photographs there are two routes: organize a shoot with a photographer, or go live for the time being with licensed stock images. If you manufacture something, photographs of your own plant and your own product work far better than stock. They're the only thing that shows the factory really exists.

No. At handover we train you on the panel, and for the length of the support period we fix any faults free of charge. The support period and what it covers are written into the contract. For the first three months we also watch the indexing errors and the form submissions ourselves, and if we see a problem we tell you before you notice it.

The domain is registered in your name, panel access is yours, and your content and customer records can be exported whenever you want. You don't pay us a yearly license to keep the site running. Transferring the source code is a separate item: designing, writing and documenting the code is the most expensive part of the job and isn't inside the package price. If you want it, we discuss it in the meeting and write it into the contract, so the price and the scope are clear from the start.

TypeScript, Next.js and React; Node.js on the server; PostgreSQL or MariaDB for the database; and our own component set built on Tailwind CSS for the interface. Pages are produced on the server, so search engines and AI crawlers can read the content without running any JavaScript. One reason we chose this stack is how common it is: finding a developer to take over after us isn't hard.

It depends. For a standard brochure site whose content changes often it's still a reasonable choice, and we wouldn't push custom development on you. But once a dealer login, pricing that changes by user, or data exchange with another system comes into play, staying tied to a chain of plugins gets expensive. Which one is right for you is something we decide together in the first meeting.

We build the layout for the small screen first and widen it out to desktop from there. Before delivery we try it on real devices. We look at the speed measurements over mobile data too, because Google ranks on the mobile version.

Both are bought in your name and paid for by you; we take care of the setup and the redirects. If you already have a domain and a server, we work on those. The choice of server depends on the project's architecture: on shared hosting with no Node.js support we build the architecture to suit it, rather than forcing you to move server.

We will, but we need to look at the code first. The review ends in one of three answers: carry on as it is, renew it piece by piece, or rewrite it. We decide on the economics. On some projects fixing the existing code costs more than rewriting it, and we say so plainly.

We trust nothing that comes from the browser and validate everything again on the server. Passwords are stored so that they can't be reversed. Permission checks happen on the server, not in the interface, because a hidden button is not a permission boundary. Forms have rate limiting and bot verification. Card details never land on our server. Once backups are set up we run a restore test; a backup nobody has tested isn't a backup.

Either you get a virtual POS from your bank, or we use a payment institution's infrastructure. The bank's commission is usually lower and the application takes longer; with a payment institution it's the other way round. In both cases the card details are entered inside the provider's own frame and never reach us. Before you apply, we get the legal pages the providers ask for ready to publish, because otherwise applications come straight back.

The main ones: a distance selling agreement and preliminary information form (Law No. 6502), company identification details and consent for commercial messages (Law No. 6563), registration with ETBİS (the Ministry of Trade's e-commerce registry) and a KVKK data protection notice. We prepare drafts of those pages as part of the setup. But let's be plain about one thing: we are not lawyers, and the texts need to be read by your own lawyer or accountant before they go live.

That's the whole point of it. The panel is in Turkish and holds only the areas you will genuinely change; we don't fill it with hundreds of settings nobody touches. At handover we give you a screen recording or face-to-face training. You won't have to wait on us to update a price, a piece of text, an image, a blog post or a reference.

The effect of the technical fixes shows up in impression data within a few weeks. The content and authority side takes longer; depending on the competition, the age of the site and the state it starts in, that is measured in months. Don't take seriously any offer that promises first place within a few weeks.

No, and nobody can. Google's ranking algorithm isn't something anyone outside it can control. Offers that come with a guarantee usually either pick keywords nobody searches for or rely on methods that damage the site in the long run. What we promise instead is this: we give you the list of work up front, and every month we measure what happened and report it to you.

We draw up the plan: which page answers which question and meets which search. The writing is either on us, or your team writes it and we edit. In sectors where technical accuracy matters we insist that the text goes through your approval; if a wrong technical detail stays up on the site, you are the one who pays for it.

Not if it's done properly. The cause of a loss is almost always the same: old addresses not being redirected to the new ones. Before going live we draw up a redirect map covering every old address, mark removed content with a 410, and check them one by one after launch. We did exactly the same when we rebuilt our own site.

Ads is advertising you pay for per click: the results start the same day, and the visibility stops when the budget stops. The other is the site being found organically on its own merits: it takes months, but the gain carries on for a while after the work stops. One catches today's demand, the other builds up tomorrow's traffic. If your budget only stretches to one channel, the choice comes down to how urgent it is.

Consistency first: the company name, address and phone number have to be written identically on the site, on the Google Business Profile and in directories. Three different addresses give a worse result than one. After that come the duller things that actually work: the right business category, real service descriptions, the location marked up with structured data, and customer reviews. Asking for reviews is legitimate; buying them isn't.

There's a lot of hype in this area, so let's stick to what's known. Google has said outright that it doesn't use the llms.txt file. A study published in May 2026 also showed that adding schema to pages already appearing in AI Overviews didn't measurably increase how often they were cited. So we put the weight on the content: sections headed with questions, definitions that can be quoted in one sentence, dated figures and comparison tables. We still do the technical side, because it costs little, but we don't sell it as a magic answer.

Not every company does. If your customers already know you and the work comes by word of mouth, a one-off technical audit is often enough instead of a monthly agreement. Monthly work pays off when people look for your product online. If you're in a field with low search volume, we'll tell you so in the meeting.

By bank transfer and EFT for now. When you place an order, the account details and your order number appear both on screen and in your e-mail; writing the order number in the description is all we need. The online card payment setup is written and waiting, and can go live the day it's approved.

We split the project fee into stages: a payment up front, an interim payment when the design is approved, and the balance on delivery. The split is written into the quote. Card installments will be possible with whatever options the bank offers, once online payment is switched on.

Yes, for every service. Corporate clients get an e-invoice or an e-archive invoice, individual clients an e-archive invoice. Sending us your invoicing details on the order form is enough.

It depends on how far the work has got. If we haven't started, we pay back everything we've received. If part of it is finished, we deduct the price of the completed items, refund the rest and send you the breakdown in writing. Work we've already delivered can't be taken back. Items whose money goes to third parties, such as the domain, hosting and advertising budget, can't be refunded either; that money isn't sitting with us. The detail is on /iade-ve-teslimat.

Yes, before we take any payment. The contract sets out the scope list, the delivery schedule, the number of revisions, the payment plan, who the code goes to and the support terms. We also write down what isn't included; every argument about scope we've seen came from those lines being missing.