Siteimp includes a built-in Help Drawer so support is available beside the screen you are using. Instead of leaving the app, searching the website, or trying to remember where you saw something, you can open Need help? and read the support article connected to the current screen.
The Help Drawer is designed to feel like a practical control surface, not a separate documentation maze. It explains the page you are on, points out what the page is for, and gives you a path to contact technical support when the article is not enough.
What the Help Drawer does
The Help Drawer gives Siteimp a small support layer inside the app.
It can help you:
- understand the screen you are currently viewing
- learn what a page is for
- find the next action to take
- interpret scan, monitoring, and website status information
- open technical support from the same place
- stay in context while you read help
Each major screen can have its own support article. That means the help content can be specific instead of generic.
For example, the Websites page explains your top-level workspace and website list. A Website dashboard page explains scan history, crawl expectations, ownership, and where deeper scan evidence lives.
Where to find the Help Drawer
Look for the Need help? control in the lower corner of the Siteimp window.
To open the Help Drawer:
- Open Siteimp.
- Go to the screen where you want help.
- Choose Need help?.
- Read the support article shown in the drawer.
- Use Contact tech support if you still need help.
The Help Drawer opens beside the app screen instead of taking over the whole window. This lets you compare the help article with the page you are actually using.
Why help appears inside the app
Support is most useful when it stays close to the problem.
If you are looking at a scan result, a monitoring page, or a website dashboard, you should not have to describe the page from memory. The Help Drawer keeps the article close to the exact screen it explains.
This helps in a few ways:
- you can read instructions while the page remains visible
- the article can use the same language as the screen
- the support form can include basic screen context if you contact support
- Siteimp can grow support content screen by screen
The result is less treasure hunting and more useful help in the moment.
How screen-specific help works
Siteimp maps app routes to support articles.
When you open the Help Drawer, Siteimp checks the current screen and loads the matching support file. A top-level page gets a top-level article. A detail page gets a detail article. A scan result page gets scan-result help.
This route-based approach lets the support system explain what you are looking at without needing one giant manual.
Examples:
- the Websites page has its own support article
- the Add website page has its own support article
- Website dashboards have their own support article
- Scan Results pages have their own support articles
- image, link, signal, page, metric, heading, and accessibility screens can each have focused help
- monitoring pages can explain monitoring-specific actions and status values
- settings and support pages can explain app-level controls
If a page does not have a dedicated article yet, Siteimp can show a fallback message instead of leaving the drawer empty.
What the traffic lights mean
The Need help? control includes a small traffic-light indicator.
The indicator is a quick status hint for the help system:
- green means the current screen has help content available
- orange means help is available in a fallback or incomplete state
- red can be used when Siteimp has matched a known error or important support condition
Most of the time, you will see green. That means the drawer has a support article for the current screen.
What you will see in a support article
A Help Drawer article usually explains the current screen in practical terms.
Depending on the page, it may include:
- what the page is for
- what information the page shows
- what actions are available
- what statuses mean
- how to interpret counts, cards, or tables
- what to do next
- when to use another page for deeper evidence
- when to contact support
The goal is not to repeat every button label. The goal is to explain the screen well enough that you can decide what to do next.
Using help without losing your place
The Help Drawer is intentionally not a blocking modal.
You can open it, read it, close it, and keep working. This matters when you are trying to compare instructions against the current page.
For example, while reviewing a Website dashboard, you may want to keep the page visible while reading about:
- the latest scan summary
- ownership state
- crawl expectations
- scan history
- where to run a new scan
- where to open deeper scan results
The drawer lets the help article sit beside the evidence instead of replacing it.
Opening technical support from the Help Drawer
If the article does not solve the problem, choose Contact tech support from the Help Drawer.
The support form opens inside the same drawer. It lets you describe what you were trying to do, what happened, what you expected, and how Siteimp should contact you.
When useful, you can also run diagnostics, review the results, and decide whether to include them in the final support report.
This creates a smooth path:
- Read the screen-specific help article.
- Try the suggested next step.
- Contact support from the same drawer if you are still stuck.
- Review the report before sending.
What happens after a support request is sent
After a support request is sent, Siteimp confirms the request and returns the Help Drawer to the support article for the current screen.
This keeps the drawer clean. The support form does not stay open after the request is complete, and the screen-specific help remains available.
If sending fails, Siteimp keeps the report available so you can copy it and send it by email instead.
The same articles are available on the website
The in-app support articles are also published on the Siteimp website under the in-app support section.
You can find them at:
/support/in-app/
This is useful when:
- you want to read help before opening the app
- you want to share a support article with someone else
- you are troubleshooting without access to the app
- you want a larger browser view
- you want to search through support content from the website
The app version is the most contextual because it opens the article beside the screen it explains. The website version is useful for browsing, sharing, and reading outside the app.
Why articles are duplicated on the website
Publishing the same support articles on the website gives Siteimp one support system with two useful surfaces.
Inside the app, the articles provide contextual help. On the website, they become a public support library.
This helps users and support in different ways:
- users can read help in the app or in a browser
- support can link directly to a public article
- documentation can improve over time without inventing separate explanations
- common support answers can become durable support pages
- screenshots, examples, and product explanations can point to the same material
A good support article should not be trapped in one place. Siteimp keeps the help close to the product while still making it available on the website.
Tips for using the Help Drawer well
Open the Help Drawer from the screen where the question came up. That gives you the most relevant article and keeps support context accurate if you contact support.
Read the first few paragraphs before jumping into the detailed sections. Most articles start by explaining what the screen is for and what decisions it helps you make.
Use the drawer as a companion while you work. It is meant to sit beside the app, not interrupt it.
Contact support when the article does not answer your question, when something looks wrong, or when the page behaves differently than the article describes.
Troubleshooting
I do not see the Need help control
Look in the lower corner of the Siteimp window.
If it is not visible, try resizing the window or navigating to another screen. If it still does not appear, use the support section on the Siteimp website.
The Help Drawer opened, but the article looks incomplete
Some screens may show a fallback article while dedicated support content is being prepared.
You can still contact technical support from the drawer.
The article does not match what I see
Siteimp may have changed faster than the support article.
Use Contact tech support and mention that the article does not match the screen. That kind of report is useful because it helps Siteimp improve both the product and the documentation.
I need to share the article with someone
Use the website version under:
/support/in-app/
The in-app drawer is best when you are using the app. The website version is best for sharing, reading, or linking from a support conversation.
I still need help after reading the article
Choose Contact tech support in the Help Drawer.
The support form lets you send the details from inside Siteimp and review the report before anything is sent.
Where to go next
To learn more about in-app support, read:
- Contacting Siteimp support for how to send a support request
- About Formimp for how support requests are delivered
- In-app support articles for the public copy of the app help library
The Help Drawer is the first layer of Siteimp support. It explains the current screen, keeps help close to the work, and gives you a direct path to technical support when the article is not enough.