# Merge Page Nodes

* <a href="/knowledge-base/project-configuration-kb/merge-page-nodes#page-nodes">Page nodes</a>
* <a href="/knowledge-base/project-configuration-kb/merge-page-nodes#frames">Frame nodes</a>

## Page Nodes

The default for the **Compare Mode** in <a href="/features/project-settings/recording-options" target="_blank">Project Settings > Recording</a> is *FullPathAndQuery*. Depending on your application, this can cause duplication in the Elements Explorer. Although the page node is not used to locate an element during execution, it's best to consolidate duplicate page nodes for organizational and maintenance purposes. For example:

1. Navigate to <http://www.bing.com/?123>

2. Enter text into the query box.

3. Click the Search button.

4. Notice the Elements Explorer.

   ![Element explorer with one page node](https://www.telerik.com/teststudio/documentation/assets/c13d813432d2ad430b696f5200947dd0/fig1.png)

5. Navigate to <http://www.bing.com/?456>

6. Repeat steps 2 and 3.

7. Notice the Elements Explorer.

8. The *SbFormQText* and *SbFormGoSubmit* elements are duplicated under each page node. This should not cause an Unable to locate element failure during execution, however it can make for unnecessary maintenance and disorganization in your project.

   ![Element explorer with two page node](https://www.telerik.com/teststudio/documentation/assets/3e17b6b413342a2cae14b8f590fcf92c/fig2.png)

9. To prevent duplication moving forward, change the **Compare Mode** to *FullPath*.

   ![Compare mode](https://www.telerik.com/teststudio/documentation/assets/279debdeac9fff82f76932134dcf7631/fig3.png)

10. To merge the **existing duplicates**, highlight each page and change its **CompareMode** property to FullPath.

    ![Change compare mode](https://www.telerik.com/teststudio/documentation/assets/ae51b05e0c70df13baaabbeadcd6fe1e/fig4.png)

    ![Select node](https://www.telerik.com/teststudio/documentation/assets/3e17b6b413342a2cae14b8f590fcf92c/fig5.png)

11. Elements explorer refreshes automatically and the nodes merge, the tree structure is better organized, and any maintenance needed on an element can now be done in one place.

    ![Nodes merge](https://www.telerik.com/teststudio/documentation/assets/419d02ef95c4c71f99ef97a0dcc0d655/fig6.png)

If *FullPath* is not applicable to your project, review the <a href="/features/project-settings/recording-options" target="_blank">Project Settings > Recording Options</a> page and select the Compare Mode that best suits your needs.

## Frames

An element directly under a page node is located entirely by its Find Settings. Conversely, an element within a frame must be located via the frame first.

1. Here we see a similar situation due to dynamic frame IDs.

   ![Two frame nodes](https://www.telerik.com/teststudio/documentation/assets/e8d05f821804cc23d31c294a18d647d4/fig7.png)

2. To merge duplicate frame nodes caused by dynamic frame IDs, strip the dynamic portion from each ID and use a tilde (\~) to indicate a partial match. See <a href="/getting-started/test-recording/Frames" target="_blank">this page</a> for more information on frames.

   ![New ID](https://www.telerik.com/teststudio/documentation/assets/ee6198984a6993fae577fefb349876e8/fig8.png)

3. Click **Refresh** to merge the duplicates.

   ![Merge nodes](https://www.telerik.com/teststudio/documentation/assets/0e515c73e86f047e609ccc73871ab101/fig9.png)
