“A Guy Built My Website”: How Do You Check What You Actually Received?

How Do You Check a Finished Website Before Accepting It?

To check a finished website, go through it as a customer, an owner and a future administrator—not only as someone assessing the design.

You need to establish:

1. Does it represent the business accurately?
2. Does it work on a phone?
3. Can a visitor easily make an enquiry?
4. Do you actually receive submitted forms?
5. Can Google and AI search engines understand the structure?
6. Are important actions being measured?
7. Do you own the website and the associated accounts?
8. Can another specialist take over the project if necessary?

The phrase “a guy made my website” is used conversationally by many clients when they do not know exactly who worked on it, how the project was built and what was included in the price.

It is not a criticism of independent specialists.

An experienced freelancer can build an excellent website. A large agency can also deliver a weak project.

The problem is not the number of people on the team.

The problem begins when the service is described vaguely, the quality cannot be verified and the client remains dependent on the only person with access.

A Beautiful Homepage Does Not Prove That the Website Is Finished

When accepting a new website, attention naturally goes to:

• the colours;
• the images;
• the logo;
• the animations;
• the first screen;
• the overall visual feel.

These elements matter, but they are only the visible part of the project.

A website can look convincing on the homepage and, at the same time, have:

• leftover demo content;
• forms that do not work;
• incorrect email recipients;
• a broken mobile version;
• images from another industry;
• missing legal pages;
• unindexed service pages;
• duplicate titles;
• missing conversion tracking;
• an administrator account controlled only by the contractor;
• a paid theme without an active licence;
• no backup.

This is why professional website creation in 2026 includes analysis, structure, content, UX, development, SEO, analytics, testing and maintenance—not only visual design.

Is a Ready-Made WordPress Theme a Problem?

No. Using a ready-made theme or design framework can be a completely professional solution.

A WordPress theme can provide:

• a technical foundation;
• a responsive grid;
• ready-made components;
• faster development;
• proven compatibility;
• a lower initial budget;
• easier ongoing maintenance.

The problem is not where the foundation came from.

The problem is how it was used and how it was presented to the client.

Proper Use of a Ready-Made Theme

The contractor:

• explains that a ready-made technical foundation is being used;
• adapts the structure to the business;
• removes all demo content;
• creates real copy;
• selects relevant images;
• modifies the components according to the requirements;
• optimises the mobile version;
• configures SEO and tracking;
• checks the forms;
• clarifies the licences.

Misleading Presentation

An almost unchanged demo is sold as:

• bespoke design;
• custom development;
• a completely unique website;
• a strategic UX system.

The client is not paying only for the installation of a theme. They are paying for the professional transformation of the technical foundation into a working asset for their specific business.

How Can You Recognise Almost Unchanged Demo Content?

Check Every Page

Do not review only the homepage.

Open:

• About Us;
• Services;
• every individual service page;
• Blog;
• Contact;
• FAQ;
• Terms and Conditions;
• Privacy Policy;
• the page displayed after a form is submitted;
• the 404 page;
• search results;
• categories and archives.

Leftover demo content often hides on pages that have not been added to the main menu.

Look for Suspicious Copy

Check for:

• `Lorem ipsum`;
• English headings on a Bulgarian website;
• foreign names;
• non-existent addresses;
• sample phone numbers;
• fake reviews;
• prices belonging to another business;
• services you do not offer;
• generic promises;
• copy that could belong to any business.

Check the Images

See whether they:

• show the actual service;
• are appropriate for the Bulgarian market;
• do not contain someone else’s logo;
• do not depict another industry;
• do not reuse the images from the theme demo;
• have appropriate alt text;
• are not excessively large;
• are licensed for your use.

A single irrelevant image may seem like a minor mistake, but it shows that the project has not undergone systematic QA.

A Real, Anonymised Example from Our Work

Check №1: Does the Website Accurately Represent the Business?

The website must clearly answer a potential customer’s essential questions:

• Who are you?
• What do you offer?
• Who is the service for?
• What problem do you solve?
• In which area do you operate?
• How does the process work?
• What does the customer receive?
• Why should they trust you?
• How can they contact you?

Check the Facts

Confirm:

• the company name;
• the address;
• the phone number;
• the email address;
• the opening hours;
• the prices;
• the team members’ names;
• the certificates;
• the years of experience;
• the locations served;
• the timeframes;
• the guarantees;
• the delivery or fulfilment terms.

Do not assume that the contractor understood everything correctly during the first conversation.

The client must verify the business facts, while the professional contractor must turn them into clear and consistent communication.

Check the Messaging

Weak copy often sounds like this:

• “We offer high quality.”
• “Our team is professional.”
• “An individual approach to every client.”
• “Competitive prices and excellent results.”

These phrases do not explain the specific value.

The website must show:

• exactly what you do;
• what makes it different;
• how the service works;
• what result the customer can realistically expect;
• what evidence supports your claims.

Check №2: Does the Website Work on a Mobile Phone?

A responsive theme does not guarantee a good mobile version.

The website needs to be checked on a real phone, not only by narrowing a browser window.

Check the Main Screens

• iPhone or Safari;
• Android or Chrome;
• a smaller phone;
• a larger phone;
• portrait mode;
• landscape mode, if relevant.

Check for Common Problems

• the text is too small;
• headings extend beyond the screen;
• buttons are too close together;
• the menu does not close;
• the pop-up blocks the content;
• tables make the page wider than the screen;
• images are cropped incorrectly;
• the form cannot be completed;
• a sticky element covers the CTA;
• the cookie banner hides important buttons;
• the phone number cannot be tapped;
• floating chat covers the form;
• the page scrolls horizontally.

Check the First Screen

On a mobile phone, it should quickly become clear:

• what the service is;
• where it is offered;
• who it is for;
• what the next action is.

If the visitor sees only a large image and an abstract sentence, the important information remains below the fold.

Check №3: Do the Forms and Contact Options Work?

The presence of a form does not mean that it sends messages.

Every form must be tested from start to finish.

Perform a Real Test

1. Complete all fields.
2. Use a real test email address.
3. Submit the form.
4. Check the success message.
5. Check whether the email was received.
6. Check the Spam folder.
7. Check which address it was sent to.
8. Check how the submitted data is displayed.
9. Confirm whether the user receives an automatic reply.
10. Check whether the action is recorded as a conversion.

Test the Errors

Try to:

• submit an empty form;
• enter an invalid email address;
• enter excessively long text;
• use Cyrillic characters;
• use a phone number with an international dialling code;
• submit from a mobile device;
• press the button twice.

Check the Other Contact Options

• does the phone number dial correctly;
• does the email address open a mail application;
• does the address lead to the correct map;
• do the WhatsApp, Viber or Messenger links work;
• do the social icons lead to the real profiles;
• does the calendar display the correct time zone.

A non-working form is one of the most expensive defects because the website may be receiving traffic while the business remains unaware that it is losing enquiries.

Check №4: Is There Clear Conversion Logic?

The website must guide the user towards a logical next action.

This could be:

• submitting an enquiry;
• making a phone call;
• booking;
• purchasing;
• requesting a quote;
• downloading a document;
• registering for an event;
• visiting a physical location.

Check the CTA Buttons

Every primary button must answer three questions:

1. What will happen?
2. What is expected of the user?
3. Where does the button lead?

Vague CTA phrases such as “Learn more” may be appropriate in a particular context, but they should not replace every specific action.

Clearer examples are:

• Request a quote;
• Book an appointment;
• Check available dates;
• Send an enquiry;
• Explore the service;
• Buy the product.

Check the Path to Contact

The user should not have to:

• search for the phone number in the footer;
• go through five pages;
• complete unnecessary fields;
• create an account without a reason;
• guess what the next step is.

A good website does not force every visitor to buy immediately.

It makes the right action easy for someone who is already ready.

Check №5: Has Real Measurement Been Configured?

The phrase “it has Google Analytics” is not enough.

You need to check:

• who owns the GA4 account;
• whether you have administrator access;
• whether traffic is being collected;
• whether Search Console is connected;
• whether Google Tag Manager is being used;
• which events are being tracked;
• which of them are conversions;
• whether there are duplicate events;
• whether an actually submitted form is recorded;
• whether only the opening of a chat is being counted;
• whether phone clicks are being tracked;
• whether consent settings are in place.

An Event Does Not Automatically Mean a Business Result

For example:

• opening the form;
• starting the form;
• pressing the button;
• successful submission;

are four different actions.

If a conversion is recorded as soon as the button is pressed, failed submissions may appear as real enquiries.

Request a List of the Actions Being Measured

The document must show:

Action	Event name	Conversion	How it is triggered
Submitted form	`generate_lead`	Yes	Only after successful submission
Phone click	`click_phone`	By objective	When a phone link is tapped
Sent chat message	Custom event	Yes	After an actual message
Opening the contact page	`page_view`	No	When the page loads

Check №6: Is There an SEO Foundation?

SEO does not mean only having Rank Math or Yoast installed.

Check whether the website has:

• one clear H1 per page;
• a logical H2/H3 structure;
• unique SEO titles;
• unique meta descriptions;
• readable URLs;
• an XML sitemap;
• correct indexing;
• canonical URLs;
• alt text for images;
• internal links;
• service pages for important services;
• local signals, if the business is local;
• schema, where appropriate;
• robots settings;
• a proper 404 page.

Check Whether Important Services Have Their Own Pages

A single general “Services” page containing two sentences about ten different activities is rarely sufficient for:

• a clear user decision;
• a Google Ads landing page;
• organic rankings;
• internal linking;
• AI citation.

Each important service should be explained in sufficient detail when it has a distinct user intent.

Check Indexing

After publication, check:

• whether Google can see the website;
• whether a sitemap has been submitted;
• whether important pages have a `noindex` directive;
• whether the website is blocked by `robots.txt`;
• whether the “Discourage search engines” setting remains enabled.

The last mistake is particularly risky for WordPress websites transferred from a staging to a live environment.

Check №7: Are the Required Policies and Legal Pages Present?

The required pages depend on:

• the type of business;
• the country;
• how data is collected;
• the cookies being used;
• whether online sales are available;
• payments;
• deliveries;
• user accounts.

The following should usually be considered:

• Privacy Policy;
• Cookie Policy;
• Terms and Conditions;
• trader information;
• delivery rules;
• return terms;
• payment methods;
• consent declarations in forms;
• management of cookie preferences.

This checklist does not constitute individual legal advice.

Ready-made text from a theme or generator does not guarantee that the policies are appropriate for the specific business. Where necessary, the content should be reviewed by a qualified lawyer.

Check №8: Which Licences Does the Website Use?

A WordPress website may rely on paid:

• themes;
• page builders;
• plugins;
• fonts;
• images;
• icon libraries;
• security services;
• backup services;
• form systems;
• translation plugins;
• optimisation tools.

Request a list containing:

Component	Licence owner	Term	Renewal	What happens after termination
Premium theme	Client or contractor	Annual / perpetual	Who pays	Does access to updates stop
Page builder	Client or agency	Annual	Price	Does the website continue to work
Form plugin	Client or agency	Annual	Price	Is the functionality retained
Stock images	As per the licence	As per the provider	Not always	Is commercial use permitted

What Does “the Website Continues to Work” Mean?

Some premium plugins continue to function after the licence expires, but:

• they do not receive updates;
• they do not receive security fixes;
• there is no support;
• new features are unavailable;
• future compatibility is not guaranteed.

This is why you need to know not only whether the website works today, but also how it will be maintained in six or twelve months.

Check No. 9: Who owns the website and the access credentials?

The business should control at least:

• the domain;
• DNS;
• hosting;
• WordPress administration;
• backups;
• GA4;
• Google Tag Manager;
• Search Console;
• business email accounts;
• the CDN;
• form systems;
• CRM integrations;
• paid accounts when purchased by the client.

The contractor may have a separate administrator profile.

They should not be the only person who can log in.

Request separate profiles

Do not use one shared WordPress administrator account for everyone.

Create:

• a dedicated client administrator;
• a separate developer profile;
• separate roles for editors;
• individual profiles for future contractors.

This allows access to be removed without changing one shared password and without losing the history of who changed what.

Check the recovery email addresses

Even if you know the password, the account may remain dependent on the contractor if:

• the recovery email belongs to them;
• the phone used for two-factor authentication belongs to them;
• the domain is registered in their account;
• hosting sends confirmations only to them.

Control means that the business can restore access independently.

The broader checklist for accounts, contracts, and reporting is described in our guide on how to choose a digital partner without losing control of your business.

Check No. 10: Are there backups and a recovery plan?

“The hosting provider makes backups” is not a sufficient explanation.

Check:

• how often backups are created;
• how long they are retained;
• whether they include the files;
• whether they include the database;
• whether a copy exists outside the same server;
• who can restore them;
• when a restore was last tested;
• what happens before a plugin update;
• whether there is a staging environment.

A backup that has never been tested is only an assumption.

Request at least one final archive when the website is handed over, together with instructions for restoring it.

Check No. 11: Is the website secure and maintained?

Check:

• whether it uses HTTPS;
• whether it has a valid SSL certificate;
• whether WordPress, the theme, and plugins are up to date;
• whether there are unused plugins;
• whether there is a default admin username;
• whether two-factor authentication is enabled;
• whether login attempts are limited;
• whether security monitoring is in place;
• whether forms are protected against spam;
• whether responsibility for updates is documented.

More plugins do not mean more functionality

Every additional plugin may add:

• a security risk;
• a conflict;
• slower performance;
• licence dependency;
• problems with future updates.

Ask for an explanation of the main plugins and remove unnecessary ones after verification.

Do not delete a component simply because you do not understand its purpose. Create a backup first and confirm its dependencies.

Check No. 12: Does the website load well enough?

A PageSpeed score is useful, but it should not be the only criterion.

Check:

• whether the website feels fast on a mobile network;
• whether the main content appears without a long wait;
• whether elements shift while loading;
• whether a large video blocks the first screen;
• whether images are optimised;
• whether unnecessary scripts load;
• whether caching works;
• whether problems appear after cookie consent;
• whether forms work when optimisation is active.

A website with a high test score but a broken form is not successful.

A website with a beautiful animation that delays the main content may look impressive in a presentation and perform poorly for real visitors.

What should you receive when the website is handed over?

Practical website acceptance checklist

What should you do if you find problems?

Do not immediately start by deleting everything or commissioning a new website.

First, divide the problems into four groups.

Critical problems

These must be fixed immediately:

• forms do not work;
• access is missing;
• SSL is invalid;
• the website is blocked from indexing;
• emails are being lost;
• malware;
• no backup;
• incorrect company details;
• payments do not work.

Problems with a major impact on results

• an unclear homepage;
• poor mobile experience;
• missing service pages;
• unsuitable images;
• missing tracking;
• a slow website;
• a confusing path to contact.

Improvements

• better copy;
• new case studies;
• stronger CTA blocks;
• additional internal links;
• optimised images;
• better FAQ content.

Future development

• new languages;
• CRM;
• automation;
• online payments;
• client accounts;
• integrations;
• new product categories.

This prioritisation helps prevent spending the budget on a visual redesign while the contact form still fails to send messages.

When can a website be repaired, and when is a redesign necessary?

The existing website can be repaired when:

• the technical foundation is stable;
• the theme is maintained;
• the structure can be adapted;
• the content can be edited;
• there is no severe dependency on an obsolete builder;
• the main URLs can be preserved;
• the problems are localised.

A redesign or rebuild may be more sensible when:

• the mobile structure is fundamentally broken;
• the website is built on an abandoned theme;
• every change causes a new problem;
• there is no clear SEO architecture;
• the design cannot be adapted;
• the code is heavily dependent on the contractor;
• control over important components is missing;
• the business has changed significantly;
• the cost of repairs approaches the cost of a new project.

Our guide to the five signs that a business needs a website redesign explains when the problem is no longer an isolated defect but a weakness in the entire system.

How much does a professional audit or repair cost?

The price depends on:

• the size of the website;
• the technology used;
• the number of pages;
• available access;
• code quality;
• the condition of the theme;
• required integrations;
• SEO risks;
• the need for new content;
• whether migration is necessary.

A reliable price cannot be determined from a screenshot of the homepage alone.

First, the following must be checked:

• the frontend;
• WordPress administration;
• hosting;
• plugins;
• analytics;
• Search Console;
• forms;
• the mobile version;
• backup options.

For guidance on different project types and public price ranges, see our guide to website development prices in 2026.

The cheapest solution is not always a complete rebuild.

Sometimes several critical fixes can stabilise the project. At other times, trying to preserve a poor foundation only postpones the inevitable redesign.

How should you choose a specialist for an independent audit?

Look for a person or team capable of assessing more than the visual layer.

The audit should cover:

• WordPress;
• UX;
• mobile behaviour;
• technical SEO;
• tracking;
• forms;
• performance;
• security;
• ownership;
• conversion logic.

An important question

Ask whether the auditor only earns money if they recommend a new website.

An independent assessment should allow for three possible conclusions:

1. The website is good enough and needs minor corrections.
2. The foundation can be retained, but more substantial repairs are required.
3. Rebuilding is more sensible than continuing to make repairs.

If the answer is known before the audit begins, it is not a diagnosis.

Freelancer or agency: does it matter?

It matters only to the extent that it affects capacity, accountability, and process.

A good independent specialist can:

• communicate directly;
• work carefully;
• have deep technical expertise;
• document the project;
• hand over all access credentials;
• provide reliable maintenance.

An agency may offer:

• a UX specialist;
• a developer;
• an SEO expert;
• a copywriter;
• a designer;
• a PPC specialist;
• project management.

However, having more roles does not automatically guarantee that those people actually worked on the project.

Check:

• who will work on it;
• exactly what they will do;
• how QA is performed;
• who is accountable;
• what will be handed over;
• what happens if the main contractor is unavailable.

You are not buying an organisational label.

You are buying a specific result, process, and accountability.

Warning signs during website handover

• You receive only a WordPress password.
• You do not know where the domain is registered.
• You do not have access to the hosting account.
• There is no backup.
• The theme and plugins are linked to the contractor’s personal account.
• It is unclear which licences you must renew.
• There is no list of pages.
• No form test has been completed.
• There is no GA4, or you have read-only access.
• You do not know what is counted as a conversion.
• Some content is in another language.
• There are images from an unrelated industry.
• Policies are empty or copied without adaptation.
• No mobile check has been performed.
• Important pages are `noindex`.
• The contractor refuses to explain the technical foundation.
• Every small change depends exclusively on them.
• Questions about ownership receive vague answers.

One omission may be repairable.

A combination of many such signals shows that the project has not been handed over professionally.

Positive signs of quality work

• You receive an exact list of completed tasks.
• All pages are reviewed together.
• Forms are tested in front of you.
• The client has their own administrator profile.
• Access is separated by role.
• There is a backup and recovery plan.
• Licences are documented.
• The mobile version has been tested on real devices.
• SEO settings are documented.
• Analytics and conversions are demonstrated.
• Known limitations are explained honestly.
• There is a warranty or support period.
• It is clear how another specialist can take over the project.
• There is no hidden dependency on a personal account.
• The delivered work matches the proposal and contract.

Conclusion: do not check who made the website—check what they delivered

The phrase “some guy made my website” says nothing about quality.

One person can build an excellent project.

A large team can leave behind demo content, broken forms, and unclear access arrangements.

The right question is not:

Was it made by a freelancer or an agency?

The right questions are:

• What was promised?
• What was actually completed?
• Does the website work for visitors?
• Can the result be measured?
• Does it have an SEO foundation?
• Can the business manage access?
• Is there a backup and documentation?
• Can another specialist take over the project?

A professional website is not merely a visual product.

It is a business system that must be:

• understandable;
• measurable;
• maintainable;
• secure;
• owned by the client;
• capable of evolving.

Do not accept the website simply because it looks finished.

Accept it when you can prove that it works.

Frequently asked questions about checking a completed website

How do you check a completed website?

Check every page, the mobile version, forms, contact details, SEO settings, analytics, conversions, speed, licences, backups, and administrative access.

Is it a problem if the website uses a ready-made WordPress theme?

No. A ready-made theme can provide a good technical foundation. The problem is when an unchanged demo is sold as a bespoke design or is not adapted to the business.

How can I tell whether the contact form works?

Send a real test message from both desktop and mobile. Check that it reaches the correct email address, that the user sees a confirmation, and that a conversion is recorded only after a successful submission.

What access should I receive after a website is built?

You should control the domain, DNS, hosting, WordPress administration, backups, GA4, Tag Manager, Search Console, and the main connected services.

Should a new website have Google Analytics?

Yes, when data is collected in accordance with the applicable rules and consent settings. In addition to GA4, important events and genuine conversions must be defined.

How can I check whether the website has an SEO foundation?

Check the H1 structure, SEO titles, meta descriptions, URLs, sitemap, indexation, alt text, internal links, service pages, and Search Console.

Who should pay for the theme and plugin licences?

This should be agreed in advance. The client should know who owns the licence, how much renewal costs, and what happens when maintenance ends.

Is a redesign necessary if demo content remains?

Not necessarily. Demo content can be corrected. A redesign is more likely when there are fundamental problems with the structure, mobile UX, technology, and maintenance.

What should I receive at final handover?

Receive access credentials, a backup, a list of plugins and licences, a tracking plan, a sitemap, editing instructions, a QA report, and a description of future maintenance.

Can one freelancer build a professional website?

Yes. Quality depends on expertise, process, QA, transparency, and the handover of assets—not only on the size or legal form of the provider.