# Project analysis

> For the complete documentation index, see [llms.txt](https://www.jetbrains.com/help/go/2026.3/llms.txt).

> **Note:**
> In GoLand versions earlier than 2025.3, project analysis was called indexing.

Project analysis allows GoLand to enable smart IDE features: code completion, inspections, refactoring, navigation, finding usages, and syntax highlighting.

GoLand triggers this process after you open or clone a new project, enable or disable plugins, and switch between branches. It is also triggered after large external file updates (for example, if multiple files are created or generated when you build your project).

![Analyzing project message in the status bar](https://resources.jetbrains.com/help/img/idea/2026.3/analyzing_project_status_bar.png)

During the analysis, GoLand examines the code in your project to create a virtual map of types, methods, objects, and other code elements that make up your application. The result of this process is the project files index, which allows the IDE to provide instantaneous smart features such as coding assistance, search, navigation, and so on.

While the analysis is in progress, smart IDE features might be unavailable or partially available. However, this does not prevent you from using GoLand: you can still type code, work with VCS features, configure settings, and perform other code-unrelated actions.

## Tracking the project analysis progress

While project analysis is running, you can track its progress in the [status bar](guided-tour-around-the-user-interface.html#status-bar), which is located at the bottom of GoLand.

![Waiting for scanning to complete in the lower-right corner of GoLand](https://resources.jetbrains.com/help/img/idea/2026.3/scanning_files.png)

If you click the status bar, the Processes dialog opens, where you can find processes that are currently in progress or in queue.

![Processes dialog with project analysis tasks](https://resources.jetbrains.com/help/img/idea/2026.3/project_analysis_process_background_tasks.png)

The main processes of project analysis include:

* Scanning files: checking which files should be analyzed. This process cannot be paused or canceled.

* Analyzing project to enable smart features: examining and indexing the file contents. This process can be paused (and resumed), but not canceled.

You can check the state of each process below its progress bar. When all processes of project analysis are completed, GoLand clears the status bar. This indicates that smart IDE features (such as coding assistance and finding usages) are ready to use.

> **Tip:**
> If you want to restart project analysis, you can do so by [invalidating
> caches](invalidate-caches.html).

## Reducing the project analysis time

The amount of time it takes to analyze your project depends on its size: the more complex your project is, the more files it contains, and the more time the IDE needs to analyze it.

You can reduce the project analysis time by [excluding files and folders](#exclude-files-folders-from-project-analysis) .

> **Note:**
> If project analysis is already in progress, you cannot speed it up. However, you can make the next analysis quicker by waiting for the current process to finish and then temporarily simplifying your project.

## Exclude files and folders from project analysis

You can mark dynamically generated files and folders as excluded to speed up project analysis and improve the overall IDE performance. For example, it's recommended that you exclude compilation output folders.   Excluded files and folders are not indexed during project analysis (therefore, smart IDE features are not available for them), but they remain part of the project.

Procedure: Exclude files from project analysis

1. Go to the  Project tool window  (`Alt+1` (Windows), `⌘ 1` (macOS), `⌘ 1` (IntelliJ IDEA Classic (macOS)), `⌘ 1` (macOS System Shortcuts), `Alt+1` (XWin), `Alt+1` (GNOME), `Alt+1` (KDE), `Alt+1` (Emacs), `Alt+1` (Sublime Text), `⌘ 1` (Sublime Text (macOS)), `Ctrl+Shift+E` (VSCode), `⌘ ⇧ E` (VSCode (macOS))).

2. Right-click a file and select `Override File Type | Plain text`.

Plain text files are marked with the ![Plain text icon represented by horizontal lines](https://resources.jetbrains.com/help/img/idea/2026.3/app-client.expui.fileTypes.text.svg) icon.

Procedure: Exclude folders from project analysis

1. Go to the  Project tool window  (`Alt+1` (Windows), `⌘ 1` (macOS), `⌘ 1` (IntelliJ IDEA Classic (macOS)), `⌘ 1` (macOS System Shortcuts), `Alt+1` (XWin), `Alt+1` (GNOME), `Alt+1` (KDE), `Alt+1` (Emacs), `Alt+1` (Sublime Text), `⌘ 1` (Sublime Text (macOS)), `Ctrl+Shift+E` (VSCode), `⌘ ⇧ E` (VSCode (macOS))) .

2. Right-click a folder and select `Mark Directory As | Excluded`.

Excluded folders are marked with the ![Excluded root icon represented by an orange folder](https://resources.jetbrains.com/help/img/idea/2026.3/app-client.expui.nodes.excludeRoot.svg) icon.

### Exclude files and folders by name patterns

In some cases, excluding files or folders one by one is not convenient. For example, this may be inconvenient if your source code files and files that are generated automatically (by a compiler, for instance) are placed in the same directories, and you want to exclude the generated files only. In this case, you can configure one or several name patterns for a specific content root.

If a folder or a filename located inside the selected content root matches one of the patterns, it will be marked as excluded. Objects outside the selected content root won't be affected.

All files within excluded folders will be excluded as well.

Procedure:

1. Press `Ctrl+Alt+S` (Windows), `⌘ Comma` (macOS), `⌘ Comma` (IntelliJ IDEA Classic (macOS)), `⌘ Comma` (macOS System Shortcuts), `Ctrl+Alt+S` (XWin), `Ctrl+Alt+S` (GNOME), `Ctrl+Alt+S` (KDE), `Ctrl+Alt+S` (Emacs), `Ctrl+Alt+S` (Sublime Text), `⌘ Comma` (Sublime Text (macOS)), `Ctrl+Comma` (VSCode), `⌘ Comma` (VSCode (macOS)) to open settings and then select `Project Structure`.

2. In the Exclude files field located at the bottom of the dialog, enter a pattern. For example, enter `*_test.go` to exclude test files.

You can configure multiple patterns and separate them with the semicolon symbol (`;`).

Patterns are applied to file and directory names only. You cannot use them to match specific paths or directories (for example, `vendor/bin/*` is not supported). If a directory name matches, all its contents are excluded.

![go_exclude_files_folders_by_name_patterns](https://resources.jetbrains.com/help/img/idea/2026.3/go_exclude_files_folders_by_name_patterns.png)

> **Note:**
> Marking files or folders as excluded does not affect deployment. To learn more about deployment exclusions, refer to [Exclude files and folders from uploading and downloading](excluding-files-and-folders-from-deployment.html) .

## See also

### How tos

[Write and edit source code](working-with-source-code.html)

