CoherenceCOHERENCE

Importing from URL

How URL import works in Coherence Sites, when it works best, and what to expect from imported pages.

URL import is the fastest way to turn an existing website into an editable starting point inside Coherence Sites.

It works best as a head start, not as a promise of a pixel-perfect mirror for every kind of website.

Best-fit pages for import

Import works especially well for:

  • simple landing pages
  • feature pages
  • docs pages
  • resource hubs
  • article pages

These pages usually map cleanly into reusable sections and standard content structure.

Harder pages

Some pages are more complex by nature:

  • custom React application surfaces
  • live directories backed by product data
  • dashboards
  • deeply bespoke interactions
  • pages whose layout depends on runtime logic

For those, import may still help bootstrap the shell, but the result is usually best handled with a hybrid approach rather than expecting a perfect clone.

What the importer does

At a high level, import:

  1. captures the source page
  2. extracts structure, content, and styling cues
  3. maps the page into reusable sections
  4. creates an editable draft in Coherence Sites

That draft is the starting point for refinement.

What to expect after import

After a successful import, plan to:

  • tighten headlines and supporting copy
  • replace or reorder a few sections
  • confirm CTAs and links
  • review logos, imagery, and footer content
  • polish any section that was more custom than average

This is normal. The goal is to save the majority of the setup work and get you into an editable state quickly.

Best practices for better imports

Import one representative page first

Start with the clearest, most standard page on the site. Homepages and top-level landing pages usually tell you quickly whether the site is a good fit for block-based import.

Use imports for structure, then refine for quality

Treat the imported page like a strong first draft. If you expect it to be the final page immediately, you’ll be disappointed more often than not.

Keep complex product surfaces separate

If part of the site is really an application experience, don’t force it through the importer. Import the marketing shell, then leave the custom product surface where it belongs.

Import and editorial velocity

Import is especially valuable when:

  • you’re migrating from an older site
  • you want to reuse strong messaging quickly
  • you need the page inside a system your team can keep updating

Once the page is in Sites, the speed win comes from editing and publishing without reopening a code workflow.

Next steps