ThemeForest Cranq - WordPress Theme

How to Set Up ThemeForest Cranq for an Elementor-Based Bicycle Repair Shop Website

ThemeForest Cranq is an Elementor template kit for a WordPress website for a bike repair shop, service workshop, custom builds, and routine maintenance. This guide is not about the product listing itself, but about practical work with the kit once you have downloaded the archive: how to prepare the site, import the templates, build the homepage, configure the header, services, and booking form, and verify everything on the live front end.

Cranq has a distinctive design language: a light background, a dark service section, acid-green accents, oversized typography, service-line rhythm, and workshop photography. That means the main job for the site owner is not simply to "install the template," but to preserve the character of the finished design while replacing the demo content so it works for a real repair shop. If you only swap the text but leave random services, weak photos, and disconnected forms in place, the site may still look cohesive, but it will not generate leads.

Below, you will find a step-by-step path from WordPress preparation to testing the form and mobile responsiveness. We will also look at which pieces the Cranq homepage is built from, how to preserve the overall style while editing in Elementor, where template kit imports most often break, and which alternatives are worth considering if you need more than a template and want a full theme with a store or catalog.

What Cranq Actually Solves on a Bike Repair Website

Cranq works well when the site needs to quickly explain the shop's services and push the visitor toward booking: brake tuning, drivetrain service, wheel building, suspension work, custom builds, and regular maintenance. Based on the original visual reference, this template is clearly designed not for a quiet corporate page, but for a service business where trust in the mechanics, a clear service list, and the feeling that "they really fix bikes here" matter. You can see that in the bike-detail photography, bold hero promises, service rows, and the dark custom-build section.

Unlike a general-purpose WordPress theme, a template kit usually does not replace the entire site theme. It gives you a set of ready-made pages, sections, and styles for Elementor. In practice, that means WordPress and a compatible theme remain the foundation, Elementor handles page editing, Template Kit Import loads the kit, and the additional plugins listed on the product page power specific elements. For Cranq, the sources list Elementor, ElementsKit Lite, MetForm, and Gum Elementor Kit. That matters: before installation, do not guess why the header or form is missing. Check right away that the required free dependencies are active.

The main value of Cranq is its ready-made composition for a workshop website. It already suggests a visitor flow: first a service promise and booking prompt, then a brief positioning statement, then a list of services, followed by a custom builds section and a step-by-step process. That order works well for a local business: people do not need to read a long company story before they understand where to click and what to ask for. This guide helps turn that demo path into a real one by replacing the services, linking buttons to the form, setting up the menu, adding contact details, and checking the inquiry form.

At the same time, Cranq is not a booking system, CRM, inventory platform, or bicycle store on its own. If the shop handles bookings with complex schedules, multiple mechanics, time slots, and payments, you will need a separate booking plugin. If you want to sell bikes and parts, you will need WooCommerce and a dedicated product structure. Cranq covers the visual and content layer: pages, blocks, forms, service cards, user flow, and visual trust.

What Pages and Blocks to Expect from the Template Kit

The ThemeForest product page for Cranq lists a set of 22 templates. For a site owner, the exact number matters less than whether the kit covers the homepage, inner service pages, contact sections, forms, and possibly team, gallery, FAQ pages, plus reusable sections. Do not import everything and publish it all without checking it. Think in terms of pages and business tasks instead.

• The homepage should explain the workshop's positioning, showcase services, and lead people to booking.
• A service page should make it clear what the work includes, what stages the request usually goes through, and how to contact the mechanic.
• The contact page should include a working form, address, phone number, business hours, and a backup contact method.
• The gallery or custom builds block should show real bikes and real workmanship, not random demo photos.
• The header and footer should stay consistent across the entire site, or visitors will lose their sense of direction from page to page.

This approach helps keep the site from becoming overloaded. A small bike repair shop can start with the homepage, services, booking form, and contacts. The rest of the templates can remain as reserve sections: add an "About the Workshop" page, expand the gallery, create a landing page for seasonal tune-ups, or build a separate section for custom frames.

Who This Template Fits and When Another Option Is Better

Cranq is worth considering for bike shop owners, service counters inside retail stores, small custom build studios, suspension specialists, mobile mechanics, and agencies that need to launch a local service site quickly. The template is especially effective when the business already has photos of the workshop, bike components, mechanics at work, and a clear service list. Cranq's visual style depends on real-world detail: chain, wheel, stand, gloves, tools, and a live working environment are more persuasive than abstract icons.

If the site only needs to be a one-page business card, Cranq may feel like more than you need. Even then, the template kit can still be useful because you can take the homepage, header, footer, contact form, and a few sections from it. The key is not to drag the full set of templates onto the live site without editing. Remove extra pages from the menu and keep a clear path to services and the form instead of showing every design variation in sequence.

The template may not be the best fit for an online store with a large bike catalog, filters, cart, payments, and shipping. Cranq looks like a service website, not an ecommerce theme. WooCommerce can be added to WordPress separately, but that becomes a different project: product pages, cart, checkout, emails, taxes, shipping, filters, and catalog performance. In that kind of setup, Cranq can still work for workshop content pages, but the store itself is better built on a theme or kit that was designed around a product catalog from the start.

Another risk is expecting a "ready-made site from one import." A template kit saves time on design, but it does not know your workshop. You still need to provide real services, booking terms, photos, copy, and contact details. Without that, you get a polished demo layout with no real trust behind it. So before installation, prepare not only WordPress, but the content too.

User Roles in the Project

To roll out Cranq cleanly, it helps to divide responsibilities. The workshop owner is responsible for the service list, real photos, pricing or service ranges, contact details, and booking rules. The webmaster handles the import, technical compatibility, forms, menu, performance, and backups. A designer or content editor updates the text carefully without breaking the typography, spacing, or contrast.

If one person is doing everything, the order still matters: first technical setup, then page structure, then content, then forms, then testing. That sequence lowers the risk of beautifully styling a page only to discover later that the form is not sending inquiries or the global styles changed the appearance of the buttons.

What to Prepare Before Importing the Template Kit

Preparation for Cranq starts with the basic combination of WordPress, a compatible theme, and Elementor. Elementor's documentation separately explains system requirements and environment recommendations, and WordPress publishes its own server requirements. There is no need to lock specific versions into the article text because they change, but before installation you should confirm them in the official sources and in your hosting panel. If the site is running old PHP, has too little memory, and Elementor already opens with errors, importing a large template set will almost certainly be unstable.

It is better to import on a copy of the site or on a clean installation. A template kit can create new pages, templates, global styles, forms, and dependencies. That is not dangerous by itself, but on a live site it is easy to run into unexpected overlaps with the current theme, cache, menu, and CSS. Before importing, create a backup of the database and files, disable aggressive optimization while you edit, and make sure the user has administrator rights.

Technical Minimum

For a standard Cranq setup, prepare the following:

• A working WordPress installation with admin access.
• A compatible lightweight theme. Hello Elementor or another neutral theme without heavy visual conflicts is commonly used with Elementor.
• Elementor installed, since Cranq templates are edited in Elementor.
• The Template Kit Import plugin if you are using the official Envato import workflow.
• ElementsKit Lite, MetForm, and Gum Elementor Kit if they are required for specific widgets and forms in your archive.
• Access to permalink, menu, page, and media settings.
• Cache disabled or easily cleared during setup so you can see real changes.

This preparation seems simple, but it is exactly what usually saves time. If a section shows up as an empty block after import, the cause is often not the template itself, but an inactive widget, a missing plugin, or a cache conflict. A template kit is not magic: Elementor builds the page from containers, widgets, images, styles, and forms, and every missing piece breaks part of that chain.

Content for the Workshop

Before importing, gather the assets in a separate folder. For Cranq, you need more than a logo and phone number. Prepare service names in a consistent style, short descriptions, photos of bikes being repaired, workspace shots, contact details, address, hours, booking rules, and answers to common questions. If you offer custom builds, create at least a few "before and after" photos or project cards: bike type, goal, what was replaced, and what the rider got in the end.

It is best to reduce the service list to 5 to 7 clear items. In Cranq's source_img, you can see six service lines: Precision Tune-Ups, Brake & Drivetrain, Suspension setup, Wheel Building & Truing, Performance Upgrades, Repair & Maintenance. You do not have to copy those labels word for word in the template admin, but the structure is strong: tune-up, drivetrain, suspension, wheels, upgrades, and maintenance. For an English-language site, that could become "Full Tune-Ups," "Brakes and Drivetrain," "Suspension Setup," "Wheel Building and Truing," "Performance Upgrades," and "Repair and Maintenance."

Pre-import check: if you cannot explain each service in one sentence and name the next action after the click within 10 minutes, improve the content first. Otherwise the template will look finished, but the user journey will still be weak.

Installing Cranq Through Template Kit Import

The official Envato workflow for template kits is usually built around the Template Kit Import plugin. It lets you upload the kit archive, review requirements, install missing dependencies, and import individual templates. It is important to understand how this differs from installing a theme: a template kit archive is not uploaded through Appearance like a standard WordPress theme. If you try to install it as a theme, WordPress may report that the archive does not contain the required theme files. That is a common mistake with Elementor template kits.

Once the site is prepared, open the WordPress admin, install and activate Elementor and Template Kit Import, then go to the kit import section, upload the Cranq archive, and wait for the template list to load. If the importer shows plugin requirements, install them from that same process or through the Plugins section. The sources for Cranq list free plugins, so do not go looking for a paid dependency unless you have confirmation. If a specific widget is unavailable, check whether the related plugin is active and whether it is being blocked by your host's security policy.

An Import Order That Avoids Chaos

Do not import templates as a random list. With Cranq, it is easier to move from global parts to pages:

1. Import the kit's global styles if the importer offers that step. They define the base palette, font hierarchy, and button styling.
2. Import the header and footer if they are included in the kit and depend on ElementsKit.
3. Import the homepage, because it sets the main rhythm of the site.
4. Load the services, contacts, about page, and any additional templates you actually plan to use.
5. Import the MetForm forms if they are delivered separately from the pages.
6. Open the pages in Elementor and check for missing widgets or empty blocks.

This order works well because it establishes the visual base first, lets the pages inherit the overall style, and only then connects the menu and forms. If you do it in reverse, you may spend a long time refining an individual page only to get different buttons, spacing, and headings after importing the global styles.

First Check After Import

Right after import, do not start editing all the text. Open the Cranq homepage in Elementor, then view it on the live site. Check that the images, header, buttons, service rows, and dark custom builds block are all visible. Click the main buttons and make sure they lead either to the form, the correct section, or at least a temporary placeholder you clearly understand. If the buttons still contain empty links, do not publish the page as finished.

At this stage, it is important to distinguish a technical issue from a routine unfinished setup. If the section looks like the demo but still has your empty links, that is content work. If a block is not displayed at all or a widget shows a warning, that is a technical dependency check. If everything exists in the editor but not on the site, look at cache, publishing settings, and the header display conditions.

What the Cranq Homepage Is Made Of: Sections, Style, and the Path to Booking

The Cranq homepage works as a route for someone dealing with a bike problem or looking for a custom build. First they see a service-level promise, then proof of experience and trust, then a list of specific jobs, then a dedicated emphasis on custom builds, and finally the step-by-step way to get started. This is not a random set of attractive blocks. Each one answers a practical question: "Do you fix my problem?", "Can I trust you?", "What is included in the service?", "How do I book?", "What happens after I reach out?"

When you edit the template, keep that chain intact. Do not move the booking form into the footer if the main button promises fast contact. Do not remove the service list if the site has no other clear work catalog. Do not replace workshop photos with abstract bikes in the woods if you are selling repair services. With Cranq, the final effect comes from three layers: section structure, global styles, and real workshop data.

The Hero Block and Above-the-Fold Area

In the original reference, Cranq's opening section is built around a strong headline, two buttons, stats, and a photo of a bike drivetrain. You should not treat this area as a place for a generic slogan. It needs to tell people right away what you do and what they should do next. If the workshop specializes in city bikes, the headline should talk about repairs, maintenance, and tune-ups. If custom builds drive most of your revenue, the opening section should lead to a build consultation rather than a generic "learn more."

It is best to separate the two hero buttons by intent. The first should be booking or an inquiry, and the second should lead to services, the work gallery, or information about the shop. Do not place two buttons that go to the same destination. That may look tidy, but it does not help the visitor choose an action. Use stats carefully: years in business, number of bikes serviced, and rating figures should all be verifiable. If you do not have that data, replace the block with checkable advantages such as pre-service diagnostics, parts approval, photo updates, or a warranty for a specific type of work if you truly offer one.

Service Lines Instead of Heavy Cards

One of Cranq's distinctive traits is that services are presented as large horizontal lines rather than identical icon cards. That works well for a bike repair shop: people scan the names of the jobs, quickly spot their problem, and move forward. When editing, do not turn this block into a long catalog of 20 small services. It is better to keep 5 to 8 top-level categories and explain the details inside each service page.

Give each line a clear action: go to a service page, open the booking form with a selected service, scroll to a description block, or show more details. If the template uses arrows on the right, check the links on every line. A broken arrow in this kind of block is more noticeable than an empty text link because the user expects it to lead somewhere.

The Dark Custom Builds Section

In the reference, the custom builds section stands apart from the lighter sections: dark background, a photo of wheel work, green markers, and detailed steps. It is not there just for style. It separates a premium or more complex service from standard repairs and shows that building a bike is a process: consultation, component selection, finishing, and final setup. If your workshop really offers builds, this block is worth keeping and filling with specifics. If it does not, replace it with one of your real strengths, such as seasonal prep, suspension service, or drivetrain repair.

Do not leave demo promises in place if they do not match your actual work. For example, if the shop does not do frame painting, any mention of custom finishing should be removed or replaced with a real service. This is not only about honesty, but also about conversion: otherwise the form will attract inquiries you are not prepared to handle.

Setting Up the Global Style, Header, and Menu After Installation

After a successful import, the most important thing is not to treat the page as a collection of isolated widgets, but to configure the system as a whole. Elementor includes global colors and fonts, and the template kit may come with imported styles as well. Cranq relies on the contrast between a light background, an almost black service block, a lime accent, and large dense typography. If you change colors one widget at a time, the site will quickly become inconsistent. If you adjust the global colors carefully, the buttons, highlights, and accent panels will stay coordinated.

Open the site kit settings or Elementor global settings if they are available in your setup. Check the main colors: background, text, accent, button color, and dark section. You do not have to keep the original lime shade, but whatever you replace it with should be one clear brand accent. For a bike repair shop, colors that read well on both light and dark backgrounds tend to work best: bright green, yellow, orange, or a rich red. The main thing is to verify the contrast of the buttons and highlights.

Global Colors and Fonts

For the first pass, set up only the core system. Check headings, body text, buttons, accents, and links. Do not change every font size in each individual widget until the overall hierarchy is approved. In Cranq, the oversized headings are part of the template's character: if you make them too small, the workshop loses its athletic energy; if you make them too heavy and too long, the opening section becomes hard to read on mobile devices.

A practical order looks like this:

1. Open Elementor's global colors and define the primary text, background, accent, and dark section colors.
2. Check the homepage in the editor without changing the content.
3. Edit the global fonts for headings and body text.
4. Open a service page and the form to make sure the style applies beyond the hero section.
5. Save the changes and clear cache if the live site is still showing the old version.

If some buttons keep their old look after you change a global color, that is normal in Elementor templates: some elements may have local settings. Start by fixing the main repeated elements: hero buttons, form buttons, service cards, and arrows in the list. Do not try to overpower local settings with brute-force CSS while the widget can still be adjusted normally.

Header, Footer, and Display Conditions

For the header and footer, Cranq may rely on ElementsKit Lite features. If so, make sure the related templates are active, assigned as the header and footer, and displayed on the correct pages. If one header appears on the homepage and another appears on an inner page, the display conditions may be wrong or the WordPress theme may be injecting its own header. This often happens when the base theme already has an active menu while the imported header is not connected site-wide.

The menu should reflect the visitor's real path, not the demo version. For a bike repair shop, items like "Services," "Custom Builds," "About the Workshop," "Gallery," and "Contact" are usually enough. If you have a blog, add it only if you are ready to publish useful content regularly: chain maintenance, seasonal prep, brake pad selection, suspension care. An empty blog in the menu lowers trust.

Buttons and Anchors

The booking button should lead to the form or to the contact block. If the site is one-page, use an anchor link to the form section. If you have a separate contact page, link to that instead. In Elementor, anchors are often set through the Menu Anchor widget or a section ID. The user does not care which method you use, but you should care about the behavior: after the click, the page should smoothly or immediately land on the correct block, not open an empty address.

Required step: after setting up the menu, open the site in a private browser window and go from the first button all the way to the form. Do not test only inside the Elementor editor, because links and display conditions can behave differently there.

Service Pages, Custom Builds, and the Work Gallery

A bike repair website should quickly answer practical questions: what exactly you fix, how many stages the work takes, whether people can drop by without an appointment, what kinds of bikes you service, whether you help choose components, and where to see examples. Cranq gives you the design language for those answers, but you still need to build the answers into the pages. In this template, a strong service page usually includes an intro block, a list of included work, a process explanation, a photo, booking terms, and a link to the form.

Do not make every service look the same. Brake tuning and a custom build follow different workflows. For brakes, people want a quick repair and a clear outcome: the lever no longer feels soft, the bike brakes evenly, and the squeal is gone. For a custom build, the important parts are consultation, component selection, budget, lead time, test setup, and approval. The page should reflect those differences.

How to Describe Services Without Overloading the Page

For each key service, use the same internal structure but with different meaning:

• Symptom or goal: what brought the visitor to the page.
• What the workshop does: 3 to 6 concrete tasks without unnecessary technical overload.
• What the customer gets: the visible outcome after service.
• What needs to be clarified: bike model, brake type, component condition, urgency.
• Action: book, send a photo, call, or come in for diagnostics.

In Cranq, the service list looks best when the titles stay short and the descriptions do not try to fit the entire pricing table. It is better to move details to a dedicated page or an expandable section. If the service is complex, add a small "What to check before your visit" block: a photo of the issue, approximate mileage, unusual noises, recent crashes, or recently replaced parts.

The Gallery as Proof, Not a Photo Dump

The work gallery is there for trust, not just for attractive images. With Cranq, large close-up photos of real details are especially useful: a properly built wheel, a clean drivetrain, tidy cable routing, the workspace, a bike on the stand. If you show custom builds, add short captions: the goal, the key components, what was done, and what outcome was verified. That turns the gallery into an argument.

Do not overload the page with dozens of heavy photos. Elementor pages with large images become slow very quickly if you upload camera originals directly. Compress the images to a reasonable size, write clear alt descriptions, and check how they look on mobile. For local service SEO, a handful of strong, specific photos with clear descriptions is better than a large set of nearly identical shots with no real purpose.

The Custom Build Card

If custom builds are an important service, create a separate card template for them. You can use Cranq's visual language there: dark background, green markers, a large heading, and a bike photo. But the content needs to stay specific: "frame and fit," "groupset," "wheels," "final tuning," "test ride." That way, the visitor sees not just a beautiful bike, but the process they are paying for.

Inside Elementor, this kind of card can be built as a reusable section and duplicated for different projects. After duplication, change not only the image, but the text as well. Otherwise the pages will feel templated and do less to build trust.

MetForm Forms and the Path to a Service Booking

Cranq lists MetForm as a dependency, so it is best to treat the booking form as a separate working unit rather than a decorative block. The form's job is to collect the minimum information the workshop needs for a first response: name, contact details, bike type, service, issue description, preferred time, and an option to attach a photo if your setup supports that. The more complex the form, the more people abandon it, but a form that is too short will lead to empty inquiries.

Start by finding the imported form in MetForm or in the Elementor page block. Check which fields are actually there. If the form came in as a demo version, replace the fields with working ones. The labels on the buttons and messages in the real MetForm UI may differ depending on the version and settings, so use the MetForm documentation and your current admin panel as the reference point. Do not invent fields that do not exist in your form. Add them using the builder's standard tools.

Minimum Field Set

For a bike service booking form, this is usually enough:

• Customer name.
• Phone number or email for a response.
• Bike type: city, road, gravel, mountain, electric, or other.
• Service category: diagnostics, brakes, drivetrain, suspension, wheel, build, maintenance.
• A short description of the issue or goal.
• A preferred time for contact if the shop does not use time-slot booking.

It is better not to require the address, exact component model, serial numbers, or full service history on the first step. Those details can be clarified later. The form should help start the conversation, not replace diagnostics.

Notifications and Protection Against Lost Inquiries

After setting up the fields, check the notifications. MetForm usually includes settings for emails to the administrator and confirmation messages to the user. Enter a working workshop email address, a clear subject line, and a message structure that shows all inquiry fields. If emails are not arriving, do not rush to blame the template. A common cause is WordPress email delivery on the hosting side. In that case, use an SMTP plugin, configure the sender, and send a test email.

The form should also have a backup path. If someone does not want to fill it out, you can leave a phone number, messenger contact, or map link nearby. That does not conflict with the template: Cranq already has strong booking buttons and contact elements, and you only need to align them with the real contact method.

Checking the Form After Publishing

Do not test the form only once in the editor. Test it like a real visitor:

1. Open the page in a private window.
2. Fill out the form with test data.
3. Submit the inquiry and check the success message.
4. Check the email in the workshop inbox and the customer confirmation email if it is enabled.
5. Confirm that the email includes the selected service and the contact details for reply.
6. Check whether the message landed in spam.

If the form only works with cache disabled or only for the administrator, that is not a finished outcome. You need to check for conflicts with cache, security plugins, JavaScript optimization, and the form's loading conditions.

Practical Use Case: Launching the Homepage for a Local Bike Repair Shop

Imagine a workshop that repairs city and performance bikes, offers seasonal service, and builds bikes around the rider's needs. The goal is to prepare the Cranq homepage in one working pass so that a visitor understands the services, sees trust signals, and can submit an inquiry. This is not the final pass on the entire site, but it is already a complete launch of the core user path.

Goal and Preparation

You need a homepage with a clear opening section, six service categories, a custom builds block, a contact form, and a working menu. Before you begin, the Cranq templates should already be imported, the dependencies should be active, workshop photos uploaded, the service list prepared, and access to the mailbox confirmed.

Setup Steps

1. Assign the homepage. In WordPress, set the imported Cranq page as the static homepage if the site should open there by default.
2. Replace the hero heading with a specific promise. For example, instead of generic copy, use wording about bike repair, tuning, and custom builds. Keep the lines short because Cranq's large typography does not handle long sentences well.
3. Configure the two main buttons. The first leads to the booking form, the second to services or the gallery. Check all anchors and links.
4. Update or replace the stats. Keep only verifiable metrics. If you do not have them, use process-based trust markers such as diagnostics before work, parts approval, or final testing.
5. Bring the services in line with the real catalog. Keep 5 to 7 categories and configure the action for each one.
6. Rewrite the custom builds block. Keep it only if that service is real. Otherwise replace it with seasonal maintenance or another strong service area.
7. Set up the MetForm form. Check the fields, email notifications, and post-submit message.
8. Build the menu. Remove demo pages and keep the path to services, gallery, and contacts.
9. Check the mobile view. Large headings, buttons, photos, and service lines should fit without overlapping.

Expected Outcome

After this pass, the homepage should answer the visitor's main questions within the first few minutes: what the shop does, which services are available, what the work looks like, where to click to book, and what happens after the inquiry is sent. In the admin, you are left with an editable Elementor page, and on the live site you get a complete path from the opening section to the form.

What Can Go Wrong

The most common mistake is replacing the text but not checking the actions. The "Book a Service" button may still be in English, the form may still send to a demo email address, and the service arrows may lead to empty pages. Visually, everything looks almost finished, but the user path is broken. That is why you need to walk through the journey without administrator rights after editing.

Short takeaway from this use case: Cranq only starts working as a real workshop website when the design, services, menu, and form are connected into a single path. A beautiful hero alone or a working form alone does not solve the problem.

Checking the Outcome on the Live Site

Testing the outcome is not a formal checkbox. It is protection against hidden problems. Elementor can look fine in the editor and different on the site. Cache can show old styles. The header may not appear on every page. The form may send only to the administrator or not at all. With Cranq, which has a strong visual identity, it is especially important to test not only functionality, but also whether the design still holds together: large headings, lime accents, the contrast of the dark block, and the rhythm of the service rows.

Desktop Check

Open the homepage as a normal visitor. Start with the opening section: logo, menu, phone number, booking button, headline, photo, and stats. Then move down the page. The services should be readable, the arrows should lead where they are supposed to, the dark block should keep its contrast, and the photos should not be stretched. If a bike image looks awkwardly cropped or blurry, replace it with a better shot instead of lowering the quality of the entire section.

Mobile Device Check

In Elementor's responsive mode, check both phone and tablet. Do not stop at confirming that the blocks "fit." You need to make sure the path is still clear: the menu opens, the booking button is visible, the headline does not break into awkward lines, the photo does not cover important text, and the form is comfortable to fill out. Cranq's large typography is part of its character, but on a small screen it still needs to stay controlled.

If the service lines become too cramped, reduce the spacing and heading size in Elementor's responsive settings. Do not redesign the entire site because of one section. In most cases, it is enough to adjust a specific container, heading, or spacing values in the mobile layout.

SEO and Accessibility Check

A template kit does not do SEO automatically. After setting up Cranq, review the basics: the site page itself should already have one H1, and inside the guide or content sections of the page you should keep a logical heading hierarchy. Images need alt descriptions that explain the content: "mechanic adjusting a bike drivetrain," "custom gravel bike build," "service booking form." Do not stuff the alt text with the template name. That does not help the user.

Also check performance. Large workshop photos straight from the camera should be compressed to web size. Extra demo pages should not remain in the menu. Cache and JavaScript optimization can speed up the site, but after enabling them, always test the MetForm form and Elementor animations again. If optimization breaks the form submission, exclude the specific script or disable the problematic setting instead of leaving the form broken.

Cranq Responsiveness: How to Preserve the Template's Character on a Small Screen

Source_img shows Cranq as a long homepage with a dense opening section, expressive typography, service lines, and a dark custom builds block. On desktop, that composition feels confident: text and photos work side by side, the stats support trust, and horizontal navigation quickly moves people through the sections. On mobile, the same design can become more difficult. The large headline takes up several lines, the bike detail photo loses part of its meaning, and the booking and service buttons may fall below the first scroll.

That is why responsiveness here is not just about "checking the phone." You need to preserve the essential message: the visitor sees that this is a workshop for repairs and custom work, understands the first action, and can open services or the form. If someone lands on mobile after a broken chain, they do not need a complex showcase of every section. They need a short path: problem, service, contact. The mobile view should be tuned around that path.

The Opening Section on a Phone

Open Elementor's responsive mode and look only at the opening section. If the headline takes up too much space, shorten it for the mobile version or split the meaning between a heading and a subheading. In Cranq, large typography is part of the design, but long Russian phrases are often wider than English ones. A phrase like "professional service for bicycles of all types" can break the rhythm more than the original English heading. A shorter wording is better: "Bike Repair, Tuning, and Custom Builds" or "Bike Service for City, Road, and Trail Riding."

The booking button should stay close to the main promise. If two buttons do not fit cleanly, keep the primary button in the opening section and move the second one lower or make it less prominent. Do not hide the main contact path just to preserve symmetry. On a service website, the action matters more than perfect decorative balance.

Photos and Subject-Specific Details

In the original Cranq, the photos show real workshop detail: cassette, wheel, mechanic's hands, workspace. On mobile, you cannot simply scale those images without checking them. If a chain photo is cropped so tightly that it turns into a blurry metallic texture, it stops working as proof. In Elementor, adjust the image position for the mobile view so the important detail stays in frame instead of slipping out of the container.

For the dark custom builds block, check the contrast and the content order. On desktop, the photo and text may sit side by side. On a phone, it is often better to place a short heading first, then the photo or key points, then the action. If the build gallery becomes too long, keep 3 to 4 strong projects and add a link to the full gallery. The user should see quality, not scroll through dozens of similar shots.

Navigation and Sticky Elements

If ElementsKit is used for the header, test the mobile menu separately. The menu icon should open correctly, the items should not run off the edge, and the booking button should not overlap the list. Do not enable a sticky header just because it looks modern. For Cranq, a sticky header is useful only if it does not cover section headings or take up a third of the phone screen.

After enabling a sticky menu, move through the page from the hero to the form. Check all anchor jumps: sometimes the page scrolls under the fixed header and the visitor sees the middle of the form instead of the beginning. If that happens, adjust the anchor offset or skip sticky behavior on mobile.

Content Setup for a Local Workshop

The template helps present the service, but specifics create trust. A local customer does not choose a workshop based on design alone. They look at whether you repair their type of bike, whether they can come in quickly, whether you show real work, how to contact you, and whether their inquiry will get lost. Cranq gives you good places for those answers, but the text needs to be written for your shop, not for a generic "bike service."

Services as Search Landing Pages

Each major service can become its own landing page. For example: "brake adjustment," "drivetrain repair," "wheel building," "suspension service," or "seasonal bike prep." That helps not only with SEO, but with usability: people open a page for their specific problem and see what the service includes. Within Cranq, these pages should inherit the overall visual style while differing in content.

For each service, use a practical structure: symptom, diagnostics, what the mechanic does, which parts may be needed, how many stages the job usually includes without promising exact timing, what the customer gets after service, and how to book. Do not use the same generic phrase like "high-quality fast service" on every page. Brakes have their own warning signs: squeal, a soft lever, rotor wobble. Drivetrains have skipping, noise, poor shifting. Wheels have lateral wobble, loose spokes, or hub play.

Photos That Work Better Than Stock Images

For Cranq, your own photos matter especially. You do not need a big photo shoot. You need images that confirm the process: a bike on the stand, a clean work area, a close-up of a cassette, a wheel in the truing stand, component selection, the finished build at delivery. These shots help visitors understand that the workshop is real and pays attention to detail.

Do not use photos where the viewer cannot tell what is happening. A beautiful bike in front of a forest works for a club or travel site, but does a weaker job of explaining repair services. On a service site, "before service," "in progress," and "finished result" images are usually stronger. If in doubt, add a short caption: "cassette and chain replacement," "wheel truing," "final brake check." The caption should stay brief, but it turns the image into proof.

Text Tone and Trust Signals

Cranq's visual tone is energetic and confident. The English copy should support that without slipping into promotional noise. Simple wording works better: "We check for play, tune the shifting, and confirm any parts replacement before work begins." That is stronger than "we provide comprehensive high-quality service." For a local business, trust comes from concrete actions and clear limitations.

If you use stats, do not decorate the site with made-up numbers. You can replace numbers with process markers such as "Diagnostics Before Repair," "Parts Approved Before Installation," or "Checked After Assembly." They are less flashy, but more honest if the workshop does not have verifiable stats. If you do have real metrics, keep the source: CRM, order log, reviews, or internal reporting. A public site should be ready to answer where the number came from.

How to Maintain the Site After Launch

Once the site is published, work with Cranq does not end. An Elementor template kit remains a set of pages that needs maintenance: update contact details, change seasonal services, check the form, review the photos, and avoid breaking the global styles. A simple maintenance routine helps keep you from returning to the site only after leads stop coming in.

Monthly Check of the Inquiry Path

Once a month, walk through the visitor journey: homepage, booking button, form, test inquiry submission, email receipt, confirmation message, mobile view. This does not take much time, but it quickly reveals problems after WordPress, Elementor, MetForm, cache, or theme updates. If the workshop actively runs paid campaigns, it is better to do this check before each campaign launch.

Record the outcome briefly: the check date in your internal document, what was submitted, where the email arrived, and what changes were made. You do not need to add a check date to the article or the site itself. What matters for the team is that any staff member can tell when the form last worked and who verified it.

Seasonal Changes Without Breaking the Structure

Bike service is seasonal. In spring, demand rises for post-storage tune-ups; in summer, for quick repairs; before trips, for drivetrain and brake tuning; in winter, for custom builds and suspension service. Cranq lets you shift the emphasis without rebuilding the site. In the hero, you can change the second line; in the services block, reorder priorities; in the dark section, feature a seasonal project; in the form, update the service categories.

Do not build a new homepage for every season. It is better to keep one structure and change individual elements. That way, you do not break the menu, SEO URLs, internal links, or the familiar inquiry path. If you need a dedicated seasonal landing page, use Cranq sections as the base, but keep the homepage stable.

Updates and a Backup Plan

Before updating WordPress, Elementor, ElementsKit, MetForm, or the base theme, create a backup. After the update, check the homepage, header, form, and one inner service page. If something breaks, do not blindly run more updates. First identify the problem layer: widget, global style, cache, header, form, or theme. That approach is faster than disabling plugins at random.

Keep a backup form path available: phone, email, messenger link, or a simple contact page. If the more complex form stops working temporarily, the visitor should still have a way to reach the workshop. That matters especially for a local service business, where one lost inquiry can mean one lost customer.

How to Use the Internal Templates: Pricing, FAQ, Blog, and Contact

The Cranq product page lists not only Home, Services, and Book Appointment, but also Pricing, FAQ, Blog, Blog Single, Contact, Team, Testimonials, Coming Soon, and 404. It is easy to treat those pages as optional extras, but for a workshop website they can close important gaps. The main thing is not to publish them automatically. Each internal page should answer a specific visitor question and offer a clear next step toward booking or contact.

Pricing Without Risky Promises

The Pricing page can be useful if the workshop is willing to show service ranges or maintenance packages. But bike repair often depends on component condition, brake type, drivetrain, suspension, and parts availability. Because of that, it is usually better not to turn Pricing into a rigid price list if the actual price is always confirmed after diagnostics. A better approach is to use the page for "service starting points": basic diagnostics, seasonal maintenance, brake and drivetrain tuning, full service, or a custom build consultation.

In the text for each item, add the condition: what is included, what is not included, which parts are billed separately, and when pre-diagnostics are required. That protects against incorrect expectations. If prices change frequently, you may choose not to show exact amounts at all and instead explain the package structure and invite people to request an estimate. Cranq's design works well for that: large blocks, bold buttons, accent elements, and clear typography help separate service tiers.

How to Check the Pricing Page

After publishing, ask someone who was not involved in the project to open the page and answer three questions: what is included in the basic service, when diagnostics are needed, and where to click to book. If they cannot answer without explanation, the page is overloaded or too vague. Fix the text, not just the design.

FAQ as a Way to Reduce Unnecessary Calls

In Cranq, the FAQ works best not as a generic "what do you do?" list, but as a practical expectation filter. For a bike repair shop, good questions cover booking, diagnostics, urgent repairs, supported bike types, bringing your own parts, labor warranties, bike storage, and seasonal workload. A block like this reduces repeated clarifying calls and helps people understand whether they should send an inquiry right now.

The answers should be short but specific. Weak: "We work with different bicycles and provide quality service." Better: "We service city, road, gravel, and mountain bikes; for electric models, we ask you to confirm the motor brand and parts availability in advance." If the workshop does not service a certain type of equipment, it is better to say so clearly. Honest limits save time on both sides.

Blog and Blog Single for Local Trust

A blog only makes sense if you are ready to maintain it as a useful section. For Cranq, it can support the service niche well: "how to tell when your chain needs replacing," "why disc brakes squeal," "what to check before a bike race," "how to prep your bike after winter." Content like that can bring in search traffic and explain services without applying hard sales pressure.

Do not publish an empty category with one demo post in it. If the blog is not ready yet, remove the menu item and keep the templates in reserve. Once you have 3 to 5 practical articles, bring the section back into navigation. In Blog Single, check the title, cover image, date, author, categories, and links to services. A strong article should lead to action gently: after a post about brakes, it is reasonable to suggest brake diagnostics, but not to insert a booking button after every paragraph.

Contact and Backup Communication Channels

The Contact page in Cranq should repeat the main inquiry path, but it should not be a copy of the homepage. It makes sense to place the form, workshop address, business hours, phone number, map, arrival instructions, and important conditions there: whether advance booking is required, whether people can leave the bike, and how parts are approved. If the workshop is appointment-only, that should be visible next to the form rather than hidden in the footer.

Check that the contact details match in the header, footer, form, and contact page. A mismatch in the phone number or email is a common small problem that causes leads to get lost. If you use a map, test that it loads without issues and add the plain text address nearby. The map may fail for some users, but the text address will still be available.

Coming Soon and 404 as Working Pages, Not Decoration

Coming Soon is useful if the site is not ready yet but the workshop already wants to collect contact requests. In that case, the page should contain a short promise, a date without unnecessary specificity unless it is confirmed, plus a notification form or direct contact information. If the notification form uses MetForm Notify Me, test it just as carefully as the main booking form.

The 404 page should help the visitor get back to services or booking. Do not leave it as a visually attractive dead end. Add links to the homepage, services, contacts, and, where appropriate, a search field. On a service site, a bad URL should not turn into a blocked path.

The Elementor Editing Process: How to Change Cranq Without Breaking the Design

In Elementor, it is easy to start changing everything directly on the page: one button color, one heading size, one block spacing value. For a small change, that is convenient, but with Cranq it quickly destroys the sense of unity. The template looks strong precisely because its rhythm, buttons, green accents, dense headings, thin dividers, and dark service sections repeat across the site. If each block gets its own random settings, the site gradually turns into a set of disconnected sections.

Before large-scale editing, give yourself a simple sequence. First lock in the global colors and fonts. Then set up the header, footer, and menu. After that, work on the homepage. Only then move to inner service pages, FAQ, contacts, and blog. That order matters: an inner service page should inherit the system you have already approved, not force you back into global styles after every block.

Duplicating Sections Instead of Copying Chaos

If you need several similar service blocks, duplicate a Cranq section and change the content inside the established structure. For example, for a "Brakes and Drivetrain" page, you can reuse a section with a large heading, a component photo, a list of tasks, and a booking button. For a "Suspension Setup" page, keep the same compositional principle but replace the photo, text, and validation points. That keeps the site recognizable while giving each page its own purpose.

Do not duplicate the entire homepage just to build one service page. That creates extra templates, complicates the menu, and increases the risk of duplicate content. It is better to save reusable sections as Elementor templates if your setup supports that, and insert them only where needed. After every duplication, check the links: the button in the new section should not lead to the old service or to a leftover demo anchor.

How to Edit Text for Large Typography

Cranq's oversized headings work best with short phrases. Russian is often longer than English, so a literal translation can damage the layout. Instead of a long phrase like "Professional bicycle servicing for all levels of repair complexity," it is better to write "Bike Repair and Tuning" and move the details into the subheading. That is not oversimplification. It is adapting the copy to the form the template is built to support.

Check headings in three places: desktop, tablet, and phone. If a heading breaks into one short last line or overlaps the photo, rewrite it. You do not always need to reduce the font size. Sometimes it is enough to remove one word, replace a long noun with a verb, or move part of the explanation into the next paragraph.

Revisions and Change Control

Before making major changes to a page, create a copy or save a revision. Elementor and WordPress usually let you return to previous states, but you should not rely on that as your only protection. Be especially careful with global styles and header templates: one change there can affect the entire site.

It is useful to keep a short change list: what was changed, where it appears, and what needs to be checked. For example: "accent color updated," "hero button links replaced," "form fields updated," "mobile hero heading shortened." A list like that helps you find the cause quickly if something starts looking different after an update or cache clear.

Local SEO and Trust: What to Refine After the Visual Build

A template kit gives you the structure and appearance, but search engines and real users judge the page by its content, speed, clarity, and credibility. For a bike repair shop, local intent is especially important: people are searching for nearby repairs, a specific problem, or seasonal bike prep. Cranq helps present those services well, but the pages still need to answer those searches in a meaningful way.

Page URLs and Service Headings

Do not leave demo page URLs in place. For a service, it is better to use a short clear URL tied to the task: /remont-tormozov/, /nastroika-transmissii/, /sezonnoe-obsluzhivanie/. If the site already uses English URLs, switching them on a Russian-language project should be handled carefully with redirects, but on a new site it is easier to make the URL structure logical from the start.

The title of a service page should reflect the real work. You do not need to mention Cranq or Elementor every time. The visitor cares more about understanding the service: "Brake Repair and Adjustment," "Wheel Building and Truing," or "Bike Setup Before the Season." The template name makes sense in a webmaster guide, but not in the public heading on the workshop page.

Microcopy That Builds Trust

On a service site, trust is often built through short clarifying phrases. Under the booking button, you can write: "We will reply and confirm the details before repair begins." Next to the form: "If the issue is urgent, call us." In the custom builds block: "Component choices are confirmed before ordering." These phrases do not replace legal terms, but they reduce user hesitation.

In Cranq, microcopy like this works best as short lines or small chips so it does not break the visual density. Do not turn the hero into a long set of instructions. A strong opening section speaks briefly, and the details come later: in services, FAQ, contacts, and work pages.

Structured Data and SEO Plugins

Cranq itself is not an SEO plugin and should not try to take on that role. For meta descriptions, sitemaps, breadcrumbs, and structured data, use a separate trusted SEO plugin if your project already relies on one. The important part is not to create conflict with Elementor templates: the visual page heading and the SEO title in the plugin may differ, but they should still refer to the same service.

For a local business, consistency in the workshop name, address, and phone number is especially important. They should match on the contact page, in the footer, in service cards, and across external business profiles. If the address changes, update it everywhere. A visitor who sees one phone number in the header and another on the contact page will not waste time figuring out which one is correct.

Speed and Indexing After Publishing

After setup, check which pages should actually be open for indexing. Draft demo pages, test service variants, and imported duplicates should not end up in the menu or sitemap. Remove them or keep them unpublished. A template kit can create more pages than you use in the first launch, and that is fine as long as you control what is public.

Performance most often suffers because of images. A bike repair shop needs good photos, but not oversized originals. Compress them, use sensible dimensions, and do not place the same heavy image in several spots without a reason. After enabling optimization, test the form and buttons again. A fast site with a broken booking path does not meet its business goal.

Safe Improvements Without Editing the Core

With a template kit, there is almost always a temptation to "tweak the look a little." You can do that, but safely: through Elementor settings, global styles, a child theme, the Customizer, or a small CSS addition. Do not edit WordPress, Elementor, MetForm, ElementsKit, or the imported archive files directly. After updates or re-imports, those changes are easy to lose.

Improving Focus Visibility for Buttons

On a bike repair shop site, the booking button is the main action. If the keyboard focus becomes hard to see after you customize the brand colors, keyboard users will have trouble knowing where they are. In WordPress, you can add a small CSS snippet through Appearance and Customize, or through your theme's safe additional CSS field. This is a careful CMS practice, not an official Cranq feature, so test it on a site copy first.

.elementor-button:focus-visible,
.elementor-form button:focus-visible {
  outline: 3px solid #c8ff3d;
  outline-offset: 3px;
}

This snippet does not change the behavior of the form or interfere with inquiry submission. It only makes focus more visible for Elementor buttons and form buttons. After adding it, open the page, press Tab, and make sure the focus is visible on the booking button, form button, and menu links. If the style conflicts with your brand, remove the snippet or change the color to a brand accent with sufficient contrast.

Localization Without Rewriting the Template

If imported blocks still contain English labels, translate them where they exist as normal Elementor text. Menu items, buttons, service headings, and form messages can all be changed directly in the editor. System messages in MetForm and WordPress are better translated through the plugin settings or the standard translation mechanism if it is available. There is no need to hunt through plugin files and edit the text manually.

Connecting Booking or a CRM

Cranq does not replace a scheduling system. If the workshop needs time slots, multiple mechanics, and inquiry statuses, you can use Cranq as the visual storefront and hand booking off to a separate booking plugin or CRM form. The rollout order is straightforward: first set up Cranq pages and buttons, then connect the external booking form or widget, then replace the button link and test the submission flow. A possible conflict point is cache and script optimization. The rollback path is simple too: return the button to a standard MetForm form or a contact block.

You can only call that an official integration if the specific service documents it. If it does not, describe the setup honestly: Cranq presents the service and leads to action, while a separate tool accepts and stores the booking request.

Why Cranq May Display Incorrectly and How to Find the Cause

Problems with Elementor template kits are often similar, but Cranq has its own sensitive areas: the header and booking buttons, the service rows, the dark custom builds block, MetForm forms, and the oversized typography. Below is a practical diagnostic path without risky actions. Move from simple to complex: dependency, import, display conditions, cache, responsiveness, and form behavior.

After Import, Some Blocks Are Empty or Widgets Are Missing

Symptom: the page opens, but some blocks are empty, Elementor shows a warning instead of a widget, or a section looks different from what you expected. Possible cause: the plugin required by the imported template is not active, or the import did not complete properly. For Cranq, check the dependencies listed on the product page: Elementor, ElementsKit Lite, MetForm, and Gum Elementor Kit.

What to check: open the plugin list, confirm that all dependencies are active, then reopen the page in Elementor. If the importer showed warnings, return to the template list and check which elements failed to import. How to fix it: activate the missing plugins, re-import the specific template, or replace the unsupported widget with a standard Elementor widget. If re-importing creates a duplicate page, delete the extra draft copy instead of publishing both.

The Header or Footer Does Not Appear on Every Page

Symptom: the Cranq header appears on the homepage, but a service page shows the base theme header or an empty area instead. Possible cause: the header template is not assigned globally, the ElementsKit display conditions apply only to one page, or the base theme outputs its own header. What to check: whether the header/footer builder is active, the display conditions, the WordPress menu assignment, and the page layout for the specific page.

How to fix it: assign the header and footer site-wide or to the required pages, disable the duplicate theme header in the theme settings, and verify the menu. If the issue appeared after switching themes, roll back to the previous theme or temporarily use a neutral theme so you can separate the theme conflict from the kit settings.

The Booking Button Goes to the Wrong Place

Symptom: a button in the hero, service row, or dark block opens an empty page, a demo URL, or nothing at all. Possible cause: demo links were left in place after import, the section anchor was changed, or the contact page is not published. What to check: the links on all major buttons, the ID of the form section, the page's published status, and the behavior in a private browser window.

How to fix it: define one main booking path: an anchor to the form, a dedicated contact page, or an external booking service. Then replace the links on every button that promises booking. If you use an anchor, test it while logged out, because the Elementor editor can hide the problem.

The Form Submits, but No Email Arrives

Symptom: the user sees a successful submission, but the workshop never receives the email. Possible cause: standard WordPress mail delivery is blocked by the host, the sender email does not match the domain, the message goes to spam, or the MetForm notifications are configured for the wrong address. What to check: the admin email, the form notification settings, the spam folder, and the SMTP plugin log if one is installed.

How to fix it: set up SMTP delivery, use a domain-based email address, and test with a sample inquiry. If the problem started after enabling JavaScript optimization, temporarily disable the suspect setting and test the form again. Once you identify the cause, re-enable optimization gradually.

The Live Site Styles Look Different from the Editor

Symptom: the page looks correct in Elementor, but on the live site the buttons, spacing, or fonts are off. Possible cause: cache, stale generated Elementor CSS files, an optimization conflict, or local theme styles. What to check: cache clearing, CSS regeneration in Elementor tools, and disabling CSS/JS minification during diagnostics.

How to fix it: clear the site and browser cache, use Elementor's CSS regeneration tool, and then open the page in a private window. If the only thing that helps is disabling optimization, configure exclusions for Elementor scripts and styles or leave the problematic feature turned off. Do not cover up the problem with dozens of CSS lines until you understand which layer is breaking the style.

The Mobile Version Loses the Meaning of the Opening Section

Symptom: the heading is too long, the buttons wrap awkwardly, the photo crops out an important part of the bike, or the stats take up too much space. Possible cause: the demo copy was replaced with longer text, but the mobile sizes and spacing were left unchanged. What to check: responsive heading settings, container order, photo size, spacing between buttons, and stats visibility.

How to fix it: shorten the mobile heading, adjust typography size only for the mobile view, check the order of the blocks, and remove secondary metrics if they get in the way of booking. The rollback path is to restore the previous Elementor responsive values or recover the page from a revision.

Limitations It Is Better to Know Up Front

Cranq does not eliminate the normal work involved in running a WordPress site. A template kit does not guarantee compatibility with every plugin stack, does not optimize your server, does not configure email, and does not replace a content strategy. If the site already runs a heavy theme, multiple page builders, aggressive cache layers, and outdated plugins, any Elementor template import can create conflicts. The best way to reduce risk is to use a clean base, create a backup, and test step by step.

The second limitation is the quality of your content. Cranq's demo photos create the right mood, but the real site has to show your workshop. If you leave generic or borrowed images in place, the site may still look polished, but it will not persuade a local customer. This is especially visible in the custom builds and services blocks, where the image needs to support the text.

The third limitation is forms and booking. MetForm helps collect inquiries, but full scheduling, mechanic management, deposits, booking cancellation, and multi-channel notifications require a separate solution. Do not promise online time-slot booking if the form only sends an email. It is better to say honestly: "Send us a request, and we will confirm the details and suggest a time."

The fourth limitation is support and updates. Marketplace pages and documentation can change, and the dependency list may change with them. Before rollout, check the product page and the official plugin pages again. If a widget in the imported kit depends on a plugin you do not want to use, plan in advance to replace that widget with a standard Elementor element.

Questions That Usually Come Up When Working with Cranq

Can I install Cranq like a regular WordPress theme?

No, not if you have the Elementor template kit version. It needs to be imported through the appropriate template kit importer and then edited in Elementor. The standard WordPress theme installer expects a different file structure, so it may report an archive error.

Do I need to install every plugin listed on the product page?

If specific Cranq templates use widgets from those plugins, then yes, the dependencies are required. According to the sources, Cranq lists Elementor, ElementsKit Lite, MetForm, and Gum Elementor Kit. If you are not using some of the pages, some dependencies may be less critical, but before removing anything, check those pages in Elementor and on the live site.

Why did the header not appear after import?

Most often, the header was imported as a separate template but was not assigned to the site or activated through the required builder. Check ElementsKit settings, display conditions, the WordPress menu, and the page layout. Also make sure the base theme is not outputting a second header on top of the imported one.

Can I use Cranq without Elementor Pro?

The product page lists free plugins in the dependency stack, but you should confirm the exact template set in the current listing and importer. If the importer requires a paid component, do not ignore the warning. First check which section depends on it, then decide whether your site actually needs that section.

How can I tell whether the MetForm form is configured correctly?

The correct test is simple: send a test inquiry as a normal visitor, wait for the success message, check the workshop inbox, and confirm that all inquiry fields are readable. If the email does not arrive, check notifications, SMTP, and cache or JavaScript optimization.

Can I repurpose Cranq for a different kind of service business?

Technically, Elementor pages can be adapted for another type of service, but Cranq's identity is rooted in a bike workshop: component photography, the service list, the custom builds block, and the athletic visual tone. For electronics repair, auto service, or another workshop type, it is usually easier to choose a template closer to that niche than to completely rewrite Cranq's subject matter.

What should I do if the template looks worse after I change the colors?

Roll back to the kit's global colors or to a saved page revision. Then adjust the palette systemically rather than one widget at a time: primary text, background, accent, buttons, and dark sections. Check the contrast in the opening section and in the form. If the brand color is too weak, use it in details and choose a stronger contrasting shade for buttons.

When ThemeForest Cranq Is a Good Choice

Cranq is worth using if you need a fast, visually cohesive bike repair shop website on Elementor: a homepage with a strong above-the-fold area, clear services, an emphasis on custom builds, a contact form, and a modern service-focused presentation. The template works especially well when the workshop has real photos, a clear list of services, and a straightforward booking process.

Before publishing, walk through the entire path again: import, dependencies, global styles, header, menu, services, form, mobile view, email, and speed. If everything matches the task, you can download ThemeForest Cranq, install it on a test copy of the site, and see how quickly the demo design turns into a working page for your bike repair business.

The main criterion is simple: after setup, the visitor should immediately understand what the workshop does, why it can be trusted, which service to choose, and how to send an inquiry. If that path works, Cranq is doing its job. If it falls apart into a nice image, empty links, and an untested form, go back to the setup and diagnostics sections before sending traffic to the site or showing it to clients.