Skip to content
Creafter LLC — Digital product studio based in New Mexico, serving businesses worldwide.
Frequently Asked Questions

Websites

15 questions Select a question to view the answer.

Creafter builds websites for businesses that need more than a basic online presence.

Projects may include:

  • corporate websites

  • service-based business websites

  • landing pages and campaign pages

  • content-driven websites

  • WordPress websites

  • custom-built websites

  • website redesigns

  • multilingual websites

The right approach depends on what the website needs to accomplish, how often content changes, which integrations are required and how much flexibility the business needs after launch.

Both.

WordPress can be a strong choice when a business needs a flexible content management system, frequently updated pages, editorial workflows or a familiar administration experience.

Custom development can make more sense when the website requires unusual functionality, deeper integrations, specialized workflows or tighter control over the application architecture.

We do not recommend custom development simply because it sounds more advanced, and we do not recommend WordPress simply because it is popular.

We choose the approach that best fits the project.

Yes.

A redesign does not automatically require replacing the entire underlying system.

We first evaluate what is already working, including:

  • content

  • URL structure

  • integrations

  • CMS

  • existing functionality

  • search visibility

  • analytics

  • technical infrastructure

If the existing foundation is healthy, we may be able to redesign the interface and improve selected areas without rebuilding the whole website.

If the current system has become difficult to maintain, slow, insecure or too restrictive, a larger rebuild may be more practical.

A website may need a redesign when it no longer supports the business effectively.

Common signs include:

  • outdated visual presentation

  • poor mobile experience

  • slow loading

  • difficult navigation

  • weak conversion performance

  • hard-to-manage content

  • broken or outdated functionality

  • inconsistent branding

  • technical limitations that prevent new features

  • declining trust or credibility

A redesign should solve identifiable problems rather than simply make the website look newer.

Yes.

Responsive behavior is a standard part of modern website development, not a separate premium feature.

The website should adapt appropriately across phones, tablets, laptops and larger screens while preserving important content and functionality.

We also consider mobile navigation, forms, touch interactions, image sizing, typography and page performance rather than simply shrinking the desktop layout.

That depends on the project, but in many cases, yes.

If the website needs regular content updates, we can provide an appropriate content management experience.

Depending on the technology, this may allow you to manage things such as:

  • pages

  • blog or Insight content

  • services

  • FAQs

  • team members

  • images

  • categories

  • selected SEO fields

Not every part of a website should necessarily be editable.

We generally make business content manageable while keeping structural or technical areas protected from accidental changes.

Yes.

Content migration may include pages, articles, images, categories or other structured information from the existing website.

The migration approach depends on:

  • the current CMS

  • the amount of content

  • content quality

  • URL structure

  • available export formats

  • whether the new site uses the same content model

Migration is also a good opportunity to identify outdated, duplicated or unnecessary content instead of automatically copying everything into the new website.

For redesigns, existing URLs should be reviewed carefully so important pages are not accidentally lost during migration.

We handle the technical SEO foundations that should be part of a professionally built website.

This can include areas such as:

  • crawlability

  • indexability

  • page titles and meta support

  • canonical URLs

  • XML sitemaps

  • redirects

  • semantic page structure

  • internal linking foundations

  • image handling

  • structured data where appropriate

  • performance considerations

However, building an SEO-friendly website is not the same as providing a complete ongoing SEO campaign.

Content strategy, keyword research, link acquisition and long-term search growth may require separate work depending on the project.

Performance is considered during development, but it would be misleading to promise a specific speed improvement before understanding the current website and project requirements.

Website performance depends on many factors, including:

  • image handling

  • frontend code

  • third-party scripts

  • fonts

  • hosting infrastructure

  • database behavior

  • integrations

  • caching

  • content choices

Our goal is to avoid unnecessary performance problems and build the website on a technically sensible foundation.

If performance is a major problem on an existing website, we can also investigate it specifically.

Yes.

Websites can be connected to external systems when suitable APIs or integration methods are available.

Examples may include:

  • CRM platforms

  • email marketing tools

  • booking systems

  • payment providers

  • ERP systems

  • analytics platforms

  • form processing services

  • customer databases

  • custom APIs

Integration requirements should be identified early because they can affect architecture, scope and testing.

We also evaluate whether a direct integration is necessary or whether an existing supported connector can solve the problem more efficiently.

Yes.

A multilingual website can be designed to support separate versions of content for different languages.

The implementation depends on the platform and how the business intends to manage translations.

Important considerations include:

  • URL structure

  • language switching

  • translated metadata

  • navigation

  • content management

  • localized images or assets where necessary

  • search-engine handling of language versions

Machine translation can be useful in some workflows, but important customer-facing content should still be reviewed for quality and accuracy.

Website development and content production are separate responsibilities unless the proposal specifically combines them.

We can structure the website around the content the project requires and help identify what needs to be prepared.

Depending on the engagement, clients may provide:

  • written copy

  • photography

  • product information

  • brand assets

  • legal content

  • team information

If content production, editing or asset creation is required from Creafter, that should be defined clearly in the project scope rather than assumed to be included automatically.

We can help configure the technical environment required for the website and advise on an appropriate hosting setup.

However, domain ownership and important third-party accounts should normally remain under the client's control.

Where possible, we prefer that the business directly owns critical assets such as:

  • domain registration

  • hosting account

  • analytics accounts

  • email services

  • payment accounts

  • other essential third-party services

This avoids unnecessary dependency on a development provider and makes long-term ownership clearer.

Hosting management or ongoing infrastructure support can be included separately when the project requires it.

Yes.

We can build focused landing pages for advertising campaigns, lead generation, product launches or specific services.

A landing page is usually more focused than a standard website page. It may be designed around one primary action such as:

  • requesting a quote

  • booking a consultation

  • registering interest

  • downloading a resource

  • purchasing a specific offer

The page structure, messaging, form length and calls to action should support that objective.

If the campaign requires tracking, we can also prepare the page for appropriate analytics and conversion measurement tools.

Yes.

A full redesign is not always necessary.

If the main problem is limited to a specific area, we can focus on that instead. Examples include:

  • improving a slow section of the website

  • rebuilding a contact or lead-generation flow

  • creating a new service section

  • fixing mobile usability problems

  • improving navigation

  • replacing an outdated integration

  • optimizing important landing pages

  • improving technical SEO issues

We prefer targeted improvements when they solve the actual problem more efficiently than rebuilding the entire website.

Still have a question?

Let's talk about your project.

Tell us what you're building, improving, or trying to solve. We'll help you figure out the right next step.